src_31ccd3a4f41f335250
- Source-provided label
- Not reported
- Evidence class
- mentioned in report
- Confidence
- Not reported
- Observed
- Oct 07, 2026 20:46 UTC
- Retrieved
- Oct 08, 2026 03:43 UTC
Server-Side Request Forgery (SSRF) through the REST API in Splunk App for Spl...
In Splunk Enterprise versions below 10.4.3, 10.2.7, and 10.0.10, a user that holds a role with the read_o11y_content capability could redirect an outbound request from Splunk App for Splunk Observa...
Reference details
- Source category
- Research & news
- Report title
Server-Side Request Forgery (SSRF) through the REST API in Splunk App for Spl...- First reported
- Oct 07, 2026 20:46 UTC
- Last reported
- Oct 07, 2026 20:46 UTC
- Catalog updated
- Oct 08, 2026 03:43 UTC
- Record ID
43267dff8bd1654bcbe0078a986ae3983e3921b5f58a81fabeaeaffbc4c1d681
Published indicators
Network indicators are visibly defanged. This page does not make them clickable or send them to another service.
No validated file hashes or network indicators are stored for this record.
Source observations
This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.
Feed collection status
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
1 sources: 0 stale, 0 needing attention, 0 paused, 1 unverified.
Review source update dates and status
- src_31ccd3a4f41f335250Collection status unverifiedLast successful batch: Unverified
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.