CVE-2026-76311

CRITICALPre-NVD 9.49.4—
EchelonGraph scoreHIGH confidence

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

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

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

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an embedded report token could download the dispatch archive for an embedded report search job and use exposed session material to access all relevant data and affect system integrity on the Splunk platform instance. The vulnerability is possible because the embedded report authorization flow does not block dispatch archive download requests before Splunk Enterprise begins sending the archive to the requester. For more information see Additional configuration for embedded reports (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/10.4/report-management/additional-configuration-for-embedded-reports) and Embed scheduled reports (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/10.4/report-management/embed-scheduled-reports) in the Splunk documentation.

CVSS v3
9.4
EG Score
9.4(high)
EG Risk
57(Track)
EG Risk 57/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
Severity94% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
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-0801 | Splunk Vulnerability Disclosure

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

Vendor Advisories for CVE-2026-76311(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 18× in last 7d / 18× 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:36 UTCEG score recompute
  2. 2026-08-21 04:36 UTCGHSA enrichment
  3. 2026-08-21 04:01 UTCEG score recompute
  4. 2026-08-21 04:01 UTCGHSA enrichment
  5. 2026-08-21 01:06 UTCEG score recompute
  6. 2026-08-21 01:06 UTCGHSA enrichment
  7. 2026-08-20 22:56 UTCEPSS rescore
  8. 2026-08-20 21:14 UTCGHSA enrichment
  9. 2026-08-20 17:23 UTCGHSA enrichment
  10. 2026-08-20 13:31 UTCGHSA enrichment
  11. 2026-08-20 13:24 UTCGHSA enrichment
  12. 2026-08-20 09:57 UTCGHSA enrichment
  13. 2026-08-20 06:06 UTCGHSA enrichment
  14. 2026-08-20 02:14 UTCEG score recompute
  15. 2026-08-20 02:14 UTCGHSA enrichment
  16. 2026-08-19 22:22 UTCEG score recompute
  17. 2026-08-19 21:40 UTCEG score recompute
  18. 2026-08-19 21:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-76311?
CVE-2026-76311 is a critical vulnerability published on August 19, 2026. In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an embedded report token could download the dispatch archive for an embedded report search job and use exposed session material to access all relevant data and affect system integrity on the…
When was CVE-2026-76311 disclosed?
CVE-2026-76311 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-76311 actively exploited?
CVE-2026-76311 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 69.7% of all scored CVEs.
What is the CVSS score of CVE-2026-76311?
CVE-2026-76311 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-76311?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76311, 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-76311

Explore →

Is Your Infrastructure Affected by CVE-2026-76311?

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

Start Free Scan →Browse All CVEs