CVE-2026-76274: Splunk Enterprise · The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium · fixed in 10.4.3 : update Splunk Enterprise when convenient.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.4.3, 10.2.7, 10.0.10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.3, 10.2.7 or 10.0.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
Splunk has released fixed versions 10.4.3, 10.2.7, and 10.0.10 that address this vulnerability. Users should upgrade affected Splunk Enterprise instances to these versions or later. Since this is not a cloud service, remediation requires applying these official patches. No alternative mitigations are specified in the advisory.
Description
CVE-2026-76274 is a vulnerability in Splunk Enterprise versions prior to 10.4.3, 10.2.7, and 10.0.10. It allows a user with the read_o11y_content capability to redirect outbound REST API requests from the Splunk App for Splunk Observability Cloud to an attacker-controlled host, potentially exposing the configured Observability Cloud API token. This occurs because the app does not fully validate the destination of outbound requests. Splunk Enterprise 9.4.x versions are not affected.