CVE-2025-20371: Unauthenticated Blind Server Side Request Forgery (SSRF) in Splunk Enterprise
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In Splunk Enterprise versions below 10.0.1, 9.4.4, 9.3.6 and 9.2.8, and Splunk Cloud Platform versions below 9.3.2411.109, 9.3.2408.119 and 9.2.2406.122, an unauthenticated attacker could trigger a blind server-side request forgery (SSRF) potentially letting an attacker perform REST API calls on behalf of an authenticated high-privileged user.
- Published
- Oct 1, 2025
- Updated
- Oct 18, 2026
- EPSS
- 0.4% · 42th percentile
- CWE
- CWE-918
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.8
- CNA · cisco
- 7.5
- 1.3 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| splunk | splunk | cpe:2.3:a:splunk:splunk |
| splunk | splunk cloud platform | cpe:2.3:a:splunk:splunk_cloud_platform |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (cisco). Independent of NVD's CPE analysis and usually ahead of it.
Splunk Splunk Cloud Platform
- 9.3.2411 and later · before 9.3.2411.109affected
- 9.3.2408 and later · before 9.3.2408.119affected
- 9.2.2406 and later · before 9.2.2406.122affected
Splunk Splunk Enterprise
- 10.0 and later · before 10.0.1affected
- 9.4 and later · before 9.4.4affected
- 9.3 and later · before 9.3.6affected
- 9.2 and later · before 9.2.8affected
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- splunk splunk9.2.0 and later · before 9.2.8
- splunk splunk9.3.0 and later · before 9.3.6
- splunk splunk9.4.0 and later · before 9.4.4
- splunk splunk10.0.0
- splunk splunk cloud platform9.2.2406 and later · before 9.2.2406.122
- splunk splunk cloud platform9.3.2408 and later · before 9.3.2408.119
- splunk splunk cloud platform9.3.2411 and later · before 9.3.2411.109
Same product
splunk: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-20253Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk EnterpriseKEV98Now
- CVE-2018-11409Splunk through 7.0.1 allows information disclosure by appending __raw/services/server/info/server-info?output_mode=json to a query, as…60This week
- CVE-2023-32707‘edit_user’ Capability Privilege Escalation59Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-20369Oct 1, 2025 · Extensible Markup Language (XML) External Entity Injection (XXE) through Dashboard label field on Splunk Enterprise26Monitor
- ← EarlierCVE-2025-20370Oct 1, 2025 · Denial of Service (DoS) through Multiple LDAP Bind Requests in Splunk Enterprise19Monitor
- Later →CVE-2025-20378Nov 12, 2025 · Open Redirect on Web Login endpoint in Splunk Enterprise24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-76351322 days apartServer-Side Request Forgery (SSRF) through the Report Notification REST API in Splunk Secure Gateway35Monitor
- CVE-2026-20252252 days apartServer-Side Request Forgery (SSRF) through Dashboard Studio PDF Export in Splunk Enterprise30Monitor
- CVE-2026-76274371 days apartServer-Side Request Forgery (SSRF) through the REST API in Splunk App for Splunk Observability Cloud26Monitor
- CVE-2026-76347322 days apartServer-Side Request Forgery (SSRF) through the Report Notifications REST API in Splunk Secure Gateway21Monitor
- CVE-2025-2038863 days apartBlind Server Side Request Forgery (SSRF) through Distributed Search Peers in Splunk Enterprise10Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.