CVE-2026-76335

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
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.8Exploit: 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 authenticated user who does not hold a role with the edit_manager_xml capability could write a malicious Splunk Web Manager Extensible Markup Language (XML) configuration. When the same user opens the affected Splunk Web Manager page, Splunk Enterprise runs attacker-controlled operating-system commands as the user account running Splunk Enterprise. The vulnerability is possible because Splunk Web does not require the edit_manager_xml capability before accepting Splunk Web Manager XML configuration changes.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
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-76335(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-22 06:55 UTCEG score recompute
  2. 2026-08-22 06:55 UTCGHSA enrichment
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 19:23 UTCGHSA enrichment
  5. 2026-08-21 16:11 UTCGHSA enrichment
  6. 2026-08-21 04:35 UTCEG score recompute
  7. 2026-08-21 04:35 UTCGHSA enrichment
  8. 2026-08-21 04:00 UTCEG score recompute
  9. 2026-08-21 04:00 UTCGHSA enrichment
  10. 2026-08-21 00:54 UTCEG score recompute
  11. 2026-08-21 00:54 UTCGHSA enrichment
  12. 2026-08-20 22:56 UTCEPSS rescore
  13. 2026-08-20 13:22 UTCGHSA enrichment
  14. 2026-08-20 09:53 UTCEG score recompute
  15. 2026-08-20 09:53 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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76335?
CVE-2026-76335 is a high 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 authenticated user who does not hold a role with the editmanagerxml capability could write a malicious Splunk Web Manager Extensible Markup Language (XML) configuration. When the same user opens the affected Splunk Web…
When was CVE-2026-76335 disclosed?
CVE-2026-76335 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-76335 actively exploited?
CVE-2026-76335 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 74.3% of all scored CVEs.
What is the CVSS score of CVE-2026-76335?
CVE-2026-76335 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-76335?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76335, 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-76335

Explore →

Is Your Infrastructure Affected by CVE-2026-76335?

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

Start Free Scan →Browse All CVEs