CVE-2026-76284

waiting for further signalsZero needs more public information before it can validate it.

GHSA-787c-75gx-5xvm ↗EUVD-2026-94585 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Splunk Enterprise >= 10.4, < 10.4.3; >= 10.2, < 10.2.7; >= 10.0, < 10.0.10; >= 9.4, < 9.4.15
fixed in 10.4.3, 10.2.7, 10.0.10, 9.4.15
CWE-707 Improper Neutralization
ETK-2026-1336Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 19h 18msince last run
35mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+108h42m
0
+2h
+4h
+6h
+8h
+10h

description

Splunk Enterprise is affected by an improper-neutralization vulnerability. The available evidence does not specify the attacker impact, affected version ranges, or access preconditions.

mitigation

Upgrade Splunk Enterprise to 10.4.3, 10.2.7, 10.0.10, or 9.4.15, as appropriate for your release branch.

fixed in 10.4.3, 10.2.7, 10.0.10, 9.4.15

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.32%23rd percentile
agent run time
35m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 20:46Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

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.

  1. 2026-10-07 20:46Z
    ghsa: trigger signal, started the run
  2. 2026-10-07 20:46Z

this entry in the feed

GET /api/v1/feed/CVE-2026-76284

{
  "etk_id": "ETK-2026-1336",
  "cve_id": "CVE-2026-76284",
  "display_id": "CVE-2026-76284",
  "ghsa_id": "GHSA-787c-75gx-5xvm",
  "euvd_id": "EUVD-2026-94585",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper neutralization in Splunk Enterprise",
  "summary": "Splunk Enterprise is affected by an improper-neutralization vulnerability. The available evidence does not specify the attacker impact, affected version ranges, or access preconditions.",
  "mitigation": "Upgrade Splunk Enterprise to 10.4.3, 10.2.7, 10.0.10, or 9.4.15, as appropriate for your release 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": [
    707
  ],
  "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.0032,
  "epss_percentile": 0.231,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 34.5634695,
  "t0_at": "2026-10-07T20:46:39.281000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T20:46:39.281000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T20:46:39.281000+00:00",
      "url": "https://github.com/advisories/GHSA-787c-75gx-5xvm"
    }
  }
}

published 2026-10-12 08:53Z
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.