CVE-2026-76285
waiting for further signalsZero needs more public information before it can validate it.GHSA-fw3v-w3rf-g749 ↗EUVD-2026-94586 ↗
description
Splunk Enterprise contains multiple internally identified flaws grouped under an improper-coding-standards weakness classification. The available evidence does not establish which earlier releases are affected, what an attacker can achieve, or what access or conditions are required.
mitigation
Update Splunk Enterprise to the applicable maintained release: 10.4.3, 10.2.7, 10.0.10, or 9.4.15. Review the vendor advisory to select the correct release for your deployment branch.
fixed in 10.4.3, 10.2.7, 10.0.10, 9.4.15
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-07 20:46Zghsa: trigger signal, started the run
- 2026-10-07 20:46Zcve.org record for CVE-2026-76285
this entry in the feed
GET /api/v1/feed/CVE-2026-76285
{ "etk_id": "ETK-2026-1335", "cve_id": "CVE-2026-76285", "display_id": "CVE-2026-76285", "ghsa_id": "GHSA-fw3v-w3rf-g749", "euvd_id": "EUVD-2026-94586", "status": "published", "anchor_state": "anchored", "title": "Coding-standard flaws in Splunk Enterprise", "summary": "Splunk Enterprise contains multiple internally identified flaws grouped under an improper-coding-standards weakness classification. The available evidence does not establish which earlier releases are affected, what an attacker can achieve, or what access or conditions are required.", "mitigation": "Update Splunk Enterprise to the applicable maintained release: 10.4.3, 10.2.7, 10.0.10, or 9.4.15. Review the vendor advisory to select the correct release for your deployment branch.", "vendor": "Splunk", "product": "Splunk Enterprise", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 10.4, < 10.4.3", ">= 10.2, < 10.2.7", ">= 10.0, < 10.0.10", ">= 9.4, < 9.4.15" ], "ecosystem": null, "fixed_versions": [ "10.4.3", "10.2.7", "10.0.10", "9.4.15" ], "package_name": "Splunk Enterprise", "purl": null } ], "cwes": [ 710 ], "cvss_score": 9.8, "cvss_src": "nvd", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "epss_score": 0.0028, "epss_percentile": 0.1903, "epss_asof": "2026-10-20", "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 46.40550388333333, "t0_at": "2026-10-07T20:46:39.808000+00:00", "signals": { "trigger_signal": { "at": "2026-10-07T20:46:39.808000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-07T20:46:39.808000+00:00", "url": "https://github.com/advisories/GHSA-fw3v-w3rf-g749" } } }
published 2026-10-12 08:48Z
last change 2026-10-21 04:45Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.