CVE-2026-76535

validatedZero produced an exploit or a check.

GHSA-8pgv-gpgf-f8wp ↗EUVD-2026-130696 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.6, < 10.6.1; >= 10.4, < 10.4.5; >= 10.2, < 10.2.9; >= 10.0, < 10.0.12; >= 9.4, < 9.4.17
fixed in 10.6.1, 10.4.5, 10.2.9, 10.0.12, 9.4.17
CWE-287 Improper Authentication
ETK-2026-4967Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1h18mTTV
42mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+78magent stopped
0
+15min
+30min
+45min
+60min

description

Splunk Enterprise releases before 10.6.1, 10.4.5, 10.2.9, 10.0.12, or 9.4.17 are affected by an authentication bypass in RapidDiag task collection. An unauthenticated attacker may execute SPL searches with an authenticated user's access, potentially exposing or altering data and configuration; exposure requires RapidDiag requests to accept an empty shared secret.

mitigation

Upgrade Splunk Enterprise to 10.6.1, 10.4.5, 10.2.9, 10.0.12, or 9.4.17, as appropriate for the deployed release branch. Ensure RapidDiag task collection does not accept an empty shared secret while upgrades are being deployed.

fixed in 10.6.1, 10.4.5, 10.2.9, 10.0.12, 9.4.17

check
available
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.
deterministic
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.
–
agent run time
42m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-19 19:55Z
Δ 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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-19 19:55Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4967",
  "cve_id": "CVE-2026-76535",
  "display_id": "CVE-2026-76535",
  "ghsa_id": "GHSA-8pgv-gpgf-f8wp",
  "euvd_id": "EUVD-2026-130696",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Splunk Enterprise RapidDiag",
  "summary": "Splunk Enterprise releases before 10.6.1, 10.4.5, 10.2.9, 10.0.12, or 9.4.17 are affected by an authentication bypass in RapidDiag task collection. An unauthenticated attacker may execute SPL searches with an authenticated user's access, potentially exposing or altering data and configuration; exposure requires RapidDiag requests to accept an empty shared secret.",
  "mitigation": "Upgrade Splunk Enterprise to 10.6.1, 10.4.5, 10.2.9, 10.0.12, or 9.4.17, as appropriate for the deployed release branch. Ensure RapidDiag task collection does not accept an empty shared secret while upgrades are being deployed.",
  "vendor": "Splunk",
  "product": "Splunk Enterprise",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.6, < 10.6.1",
        ">= 10.4, < 10.4.5",
        ">= 10.2, < 10.2.9",
        ">= 10.0, < 10.0.12",
        ">= 9.4, < 9.4.17"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "10.6.1",
        "10.4.5",
        "10.2.9",
        "10.0.12",
        "9.4.17"
      ],
      "package_name": "Splunk Enterprise",
      "purl": null
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 41.50068771666667,
  "t0_at": "2026-11-19T19:55:22.841000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-19T21:13:27.684913+00:00",
      "days": 0.05422273047453704,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T19:55:22.841000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-19T19:55:22.841000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T19:55:22.841000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-76535"
    }
  }
}

published 2026-11-19 20:31Z
last change 2026-11-20 08:30Z

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.