CVE-2026-76387

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

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

In Splunk Enterprise Security versions below 8.6.1, a user who holds a Splunk Enterprise Security role that contains the mc_investigation_read capability could inject Search Processing Language (SPL) through Analyst Queue search filters, allowing for access to all relevant data and system integrity available to the scheduled searches that run for that user. The vulnerability is possible because the Analyst Queue search filter handling does not validate filter field names before the fields are included in SPL searches. For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.4/installation/users-and-roles-for-splunk-enterprise-security), Manage analyst workflows using the analyst queue in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.4/mission-control/manage-analyst-workflows-using-the-analyst-queue-in-splunk-enterprise-security), and Overview of Mission Control in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.5/mission-control/overview-of-mission-control-in-splunk-enterprise-security) in the Splunk documentation.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 21, 2026

Advisory Details (1)

Auto-updated Aug 19, 2026
No patch confirmed yet.
generic

SVD-2026-0807 | Splunk Vulnerability Disclosure

https://advisory.splunk.com/advisories/SVD-2026-0807

Vendor Advisories for CVE-2026-76387(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 17× in last 7d / 17× 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-08-21 04:35 UTCEG score recompute
  2. 2026-08-21 04:35 UTCGHSA enrichment
  3. 2026-08-21 04:00 UTCEG score recompute
  4. 2026-08-21 04:00 UTCGHSA enrichment
  5. 2026-08-21 03:22 UTCEG score recompute
  6. 2026-08-21 03:22 UTCGHSA enrichment
  7. 2026-08-20 22:56 UTCEPSS rescore
  8. 2026-08-20 14:25 UTCEG score recompute
  9. 2026-08-20 14:25 UTCGHSA enrichment
  10. 2026-08-20 13:33 UTCEG score recompute
  11. 2026-08-20 13:33 UTCGHSA enrichment
  12. 2026-08-20 13:12 UTCGHSA enrichment
  13. 2026-08-20 11:17 UTCEG score recompute
  14. 2026-08-20 11:17 UTCGHSA enrichment
  15. 2026-08-19 22:20 UTCEG score recompute
  16. 2026-08-19 21:39 UTCEG score recompute
  17. 2026-08-19 21:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-76387?
CVE-2026-76387 is a high vulnerability published on August 19, 2026. In Splunk Enterprise Security versions below 8.6.1, a user who holds a Splunk Enterprise Security role that contains the mcinvestigationread capability could inject Search Processing Language (SPL) through Analyst Queue search filters, allowing for access to all relevant data and system integrity…
When was CVE-2026-76387 disclosed?
CVE-2026-76387 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-76387 actively exploited?
CVE-2026-76387 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 79.7% of all scored CVEs.
What is the CVSS score of CVE-2026-76387?
CVE-2026-76387 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-76387?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76387, 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-76387

Explore →

Is Your Infrastructure Affected by CVE-2026-76387?

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