CVE-2026-76361

LOWPre-NVD 2.72.7—
EchelonGraph scoreMEDIUM confidence

Score 2.7 from GitHub Security Advisory (severity: LOW) published 2026-08-20. a secondary CVSS source baseline 2.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
2.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In Splunk SOAR versions below 8.6.0, a user with the "Administrator" role could use the /rest/support/connectivity/.../check_connectivity endpoint to make Splunk SOAR initiate outbound network connections to arbitrary destinations and determine whether internal hosts and ports are reachable. The Server-Side Request Forgery (SSRF) is possible because the connectivity check REST API does not sufficiently validate the destination before Splunk SOAR connects to it. For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.5.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.

CVSS v3
2.7
EG Score
2.7(medium)
EG Risk
12(Track)
EG Risk 12/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity27% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 21, 2026

References (1)

Vendor Advisories for CVE-2026-76361(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-19 02:43 UTCEG score recompute
  3. 2026-09-19 02:42 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 06:24 UTCEG score recompute
  7. 2026-09-16 06:24 UTCGHSA enrichment
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-13 10:07 UTCEG score recompute
  11. 2026-09-13 10:07 UTCGHSA enrichment
  12. 2026-09-12 15:02 UTCEPSS rescore
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-10 13:49 UTCEG score recompute
  15. 2026-09-10 13:49 UTCGHSA enrichment
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 17:31 UTCEG score recompute
  19. 2026-09-07 17:31 UTCGHSA enrichment
  20. 2026-09-06 13:48 UTCEPSS rescore
  21. 2026-09-04 21:14 UTCEG score recompute
  22. 2026-09-04 21:14 UTCGHSA enrichment
  23. 2026-09-04 05:07 UTCEPSS rescore
  24. 2026-09-02 14:12 UTCEPSS rescore
  25. 2026-09-02 00:01 UTCEG score recompute
Show 32 more
  1. 2026-09-02 00:01 UTCGHSA enrichment
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-09-01 04:40 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-08-30 19:18 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 03:44 UTCEG score recompute
  8. 2026-08-30 03:44 UTCGHSA enrichment
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-28 21:42 UTCEPSS rescore
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 07:26 UTCEG score recompute
  13. 2026-08-27 07:26 UTCGHSA enrichment
  14. 2026-08-26 14:47 UTCEPSS rescore
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-24 14:18 UTCEPSS rescore
  17. 2026-08-24 11:08 UTCEG score recompute
  18. 2026-08-24 11:08 UTCGHSA enrichment
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-21 14:50 UTCEG score recompute
  22. 2026-08-21 14:50 UTCGHSA enrichment
  23. 2026-08-20 22:56 UTCEPSS rescore
  24. 2026-08-20 17:35 UTCEG score recompute
  25. 2026-08-20 17:35 UTCGHSA enrichment
  26. 2026-08-20 16:36 UTCEG score recompute
  27. 2026-08-20 16:35 UTCGHSA enrichment
  28. 2026-08-20 13:16 UTCEG score recompute
  29. 2026-08-20 13:16 UTCGHSA enrichment
  30. 2026-08-19 22:21 UTCEG score recompute
  31. 2026-08-19 21:39 UTCEG score recompute
  32. 2026-08-19 21:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76361?
CVE-2026-76361 is a low vulnerability published on August 19, 2026. In Splunk SOAR versions below 8.6.0, a user with the "Administrator" role could use the /rest/support/connectivity/.../check_connectivity endpoint to make Splunk SOAR initiate outbound network connections to arbitrary destinations and determine whether internal hosts and ports are reachable. The…
When was CVE-2026-76361 disclosed?
CVE-2026-76361 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76361 actively exploited?
CVE-2026-76361 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.5% of all scored CVEs.
What is the CVSS score of CVE-2026-76361?
CVE-2026-76361 has a CVSS v3 base score of 2.7 (NVD).
How do I remediate CVE-2026-76361?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76361, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-76361

Explore →

Is Your Infrastructure Affected by CVE-2026-76361?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs