CVE-2026-76282
Splunk 9.4.0 – 9.4.15
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-76282 is a high-severity Improper Control of a Resource Through its Lifetime (CWE-664) vulnerability in Splunk Splunk. Its CVSS base score is 8.8 (High).
Operationally, ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-94634
Vulnerability Data
Improper Control of a Resource Through its Lifetime. Splunk addressed multiple internally identified vulnerabilities in Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15. The vulnerabilities are grouped by Common Weakness Enumeration (CWE), with one Common Vulnerabilities and Exposures (CVE) identifier…
more
assigned to each group. See Details for more information.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requires a managed development lifecycle process with integrity controls on changes, improving control of resources throughout their lifetime.
Requires designing resource lifetime controls that anticipate, withstand, and recover from stresses or attacks, mitigating improper resource control.
Directly enforces limited resource lifetime by requiring initiation from a known state and explicit termination, shrinking the window any long-lived resource weakness can be exploited.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Information deletion control ensures proper release and sanitization at end of life.
A.8.25 mandates secure SDLC practices (secure requirements, checkpoints, secure coding, testing per 8.29, developer training) that reach many but not all lifetime-control defects in CWE-664; a bounded remainder (e.g. certain runtime resource mismanagement or non-software resources) is not covered by the development-lifecycle focus.
A.8.26 only requires that security requirements (including some that could address resource lifetime) be identified and specified during development or acquisition; it does not mandate or perform any removal of the CWE-664 flaw itself from existing or produced code.
Secure architecture principles reduce lifetime control issues but are not specific to them.
Secure coding practices help avoid lifetime control bugs but do not address the full scope.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-664, a pillar-level weakness. Rules are authored against its narrower children: CWE-471.