CVE-2026-76530

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

GHSA-6vr6-2g9h-34wg ↗EUVD-2026-107635 ↗

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 SOAR < 8.7.0
fixed in 8.7.0
CWE-647 Use of Non-Canonical URL Paths for Authorization Decisions
ETK-2026-2386Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 42msince last run
31mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+4h49m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Splunk SOAR is affected by inconsistent handling of URL path representations during access-control decisions. An attacker who can reach relevant application endpoints may be able to have authorization evaluated against a different path representation than the resource ultimately accessed.

mitigation

Apply the vendor's hardening release for this issue when it is available for the deployed Splunk SOAR version. Until then, limit access to SOAR web endpoints to trusted networks and authenticated users.

fixed in 8.7.0

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 22:52Z
Δ 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

No artifact: no remotely reachable path found.

source signals

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

  1. 2026-10-21 22:52Z
    ghsa: trigger signal, started the run
  2. 2026-10-21 22:52Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2386",
  "cve_id": "CVE-2026-76530",
  "display_id": "CVE-2026-76530",
  "ghsa_id": "GHSA-6vr6-2g9h-34wg",
  "euvd_id": "EUVD-2026-107635",
  "status": "published",
  "anchor_state": "anchored",
  "title": "URL path authorization bypass in Splunk SOAR",
  "summary": "Splunk SOAR is affected by inconsistent handling of URL path representations during access-control decisions. An attacker who can reach relevant application endpoints may be able to have authorization evaluated against a different path representation than the resource ultimately accessed.",
  "mitigation": "Apply the vendor's hardening release for this issue when it is available for the deployed Splunk SOAR version. Until then, limit access to SOAR web endpoints to trusted networks and authenticated users.",
  "vendor": "Splunk",
  "product": "Splunk SOAR",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 8.7.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "8.7.0"
      ],
      "package_name": "Splunk SOAR",
      "purl": null
    }
  ],
  "cwes": [
    647
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 31.031495583333335,
  "t0_at": "2026-10-21T22:52:19.125000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T22:52:19.125000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T22:52:19.125000+00:00",
      "url": "https://github.com/advisories/GHSA-6vr6-2g9h-34wg"
    }
  }
}

published 2026-10-22 03:10Z
last change 2026-10-22 05:15Z

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.