Splunk Enterprise: verify session actions

Published · Updated · APIs and connected services · 6 min read · By Cyber Intelligence Embassy

At a glance

Splunk Enterprise: cross-site request forgery (CSRF). This 2026-07-18 case examines 14 version entries and 31 CVEs, documented releases and checks suited to detection tools, using CERTFR-2026-AVI-0888.

AI illustration: a dark cybersecurity technology space with restrained golden lighting Illustration · fictional scene
In this article

Retrospective for 2026-07-18, compiled on 27 October 2026. The date identifies the day being analysed; source publication and revision dates are recorded below.

What this advisory changes in your environment

The starting point is CERTFR-2026-AVI-0888, published on 2026-07-16. Its scope includes Splunk Enterprise, Splunk Universal Forwarder, Splunk Cloud Platform. Reported consequences are cross-site request forgery (CSRF), data integrity compromise, impact requiring vendor clarification, loss of confidentiality. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.

This case contains 14 version entries; CVE identifier count: 31. Track remediation by component: a successful overall update does not demonstrate that Splunk Enterprise and Splunk Cloud Platform each received their respective fix.

Products and versions to examine

Reference
CERTFR-2026-AVI-0888
Source first published
2026-07-16
Latest source revision available for this day
2026-07-16
Named components
Splunk Enterprise, Splunk Universal Forwarder, Splunk Cloud Platform
CVE identifiers
CVE-2026-20296, CVE-2026-8201, CVE-2026-27143, CVE-2026-8200, CVE-2026-6914, CVE-2026-24051, CVE-2026-6915, CVE-2026-27144, CVE-2026-32283, CVE-2026-20297, CVE-2026-32285, CVE-2026-39883, CVE-2026-32281, CVE-2026-28389, CVE-2026-34986, CVE-2026-8053, CVE-2026-8199, CVE-2026-28388, CVE-2026-32280, CVE-2026-29181, CVE-2026-28390, CVE-2026-32287, CVE-2026-39836, CVE-2025-47913 … (+7)
ComponentPublished condition
Splunk Enterprise9.3.x : < 9.3.14
Splunk Universal Forwarder10.4.x : < 10.4.1
Splunk Cloud Platform10.3.2512.x : < 10.3.2512.16
Splunk Enterprise9.4.x : < 9.4.13
Splunk Cloud Platform10.4.2604.x : < 10.4.2604.7
Splunk Universal Forwarder10.0.x : < 10.0.8
Splunk Enterprise10.4.x : < 10.4.1
Splunk Cloud Platform10.1.2507.x : < 10.1.2507.24
Splunk Cloud Platform10.2.2510.x : < 10.2.2510.18
Splunk Universal Forwarder10.2.x : < 10.2.5
Splunk Enterprise10.2.x : < 10.2.5
Splunk Enterprise10.0.x : < 10.0.8
Splunk Universal Forwarder9.4.x : < 9.4.13
Splunk Cloud Platform10.5.2605.x : < 10.5.2605.0

For Splunk Enterprise, the published condition is “9.3.x : < 9.3.14”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of Splunk Enterprise does not close this case.

Mechanism and prerequisites

CSRF can misuse a session that is already authenticated. Check origin validation and anti-CSRF tokens on sensitive actions alongside cookie settings; authentication does not protect every action by itself.

The primary record CVE-2026-20296, published by cisco, covers Splunk Enterprise, Splunk Cloud Platform. The retained revision is dated 2026-07-16. Its scope is presented separately from the integrations and product groupings in CERTFR-2026-AVI-0888.

The published metric for CVE-2026-20296 is CVSS 3.1, 8.3/10. The vector below describes technical prerequisites; it does not measure attack frequency or the likelihood that your deployment is compromised.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L

Attack vector
Not specified in the retained source
Prior privileges
Not specified in the retained source
User interaction
Not specified in the retained source
Complexity
Not specified in the retained source
Weakness
CWE-352

Choose the appropriate intervention

  1. Locate Splunk Enterprise instances, running releases and service owners. Record condition 9.3.x : < 9.3.14 in the ticket alongside reference CERTFR-2026-AVI-0888.
  2. Compare the installed branch with the vendor’s Splunk Enterprise release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
  3. After changing Splunk Enterprise, capture the loaded version again and verify the workflow below. Any exception needs an owner, an exposure-reduction measure and an expiry date.

Verify the fix in a real workflow

Validation scenario to adapt for Splunk Enterprise: In a test instance of Splunk Enterprise, submit a known synthetic event through the normal collection channel. Confirm receipt, timestamp and processing; check that updating the collector has not left another vulnerable agent or module installed. This is a proposed defensive check, not a claim that testing was performed against third-party systems.

Limit of case CERTFR-2026-AVI-0888: this analysis replaces neither vendor prerequisites nor investigation of your logs. Only documented versions are reproduced; no attack date or victim is invented.

Questions specific to this case

Which condition should be checked for Splunk Enterprise?

Advisory CERTFR-2026-AVI-0888 states: Splunk Enterprise — 9.3.x : < 9.3.14. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.

Why not use one fix for Splunk Enterprise and Splunk Cloud Platform?

CERTFR-2026-AVI-0888 distinguishes these components within a scope containing 14 entries. Match each branch to its own update documentation and functional check.

Which prerequisites does record CVE-2026-20296 specify?

For CVE-2026-20296, the published vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L. Verify those conditions on Splunk Enterprise, Splunk Cloud Platform before applying them to an integration named in CERTFR-2026-AVI-0888.

Sources and related reading

Practical guide : Make security event logs ready for detection

Explore the decision addressed in this case

Complete source advisory inventory

The article table may be an extract. These lists contain every affected-system entry and CVE in the specified advisory revision. They are not an inventory of your assets and do not map every CVE to every product.

Official source · CERTFR-2026-AVI-0888
Advisory revision : · Checked on :

Affected systems · 14

Original French wording is retained to avoid ambiguous translations of version conditions.

  1. Splunk Enterprise versions 9.3.x antérieures à 9.3.14
  2. Splunk Universal Forwarder versions 10.4.x antérieures à 10.4.1
  3. Splunk Cloud Platform versions 10.3.2512.x antérieures à 10.3.2512.16
  4. Splunk Enterprise versions 9.4.x antérieures à 9.4.13
  5. Splunk Cloud Platform versions 10.4.2604.x antérieures à 10.4.2604.7
  6. Splunk Universal Forwarder versions 10.0.x antérieures à 10.0.8
  7. Splunk Enterprise versions 10.4.x antérieures à 10.4.1
  8. Splunk Cloud Platform versions 10.1.2507.x antérieures à 10.1.2507.24
  9. Splunk Cloud Platform versions 10.2.2510.x antérieures à 10.2.2510.18
  10. Splunk Universal Forwarder versions 10.2.x antérieures à 10.2.5
  11. Splunk Enterprise versions 10.2.x antérieures à 10.2.5
  12. Splunk Enterprise versions 10.0.x antérieures à 10.0.8
  13. Splunk Universal Forwarder versions 9.4.x antérieures à 9.4.13
  14. Splunk Cloud Platform versions 10.5.2605.x antérieures à 10.5.2605.0
CVE identifiers · 31