PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-76294 Splunk CVE debrief

CVE-2026-76294 Improper Access Control in Field Extraction Management in Splunk Enterprise allows a user without 'admin' or 'power' roles to move field extractions or transformations to unauthorized apps. This issue exists in Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 due to insufficient validation of destination app access by the REST API.

Vendor
Splunk
Product
Splunk Enterprise
CVSS
MEDIUM 4.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-21
Original CVE updated
2026-10-22
Advisory published
2026-10-21
Advisory updated
2026-10-22

Who should care

Splunk Enterprise administrators and users with access to field extraction management should assess exposure and prioritize upgrading to patched versions or restricting access to prevent unauthorized changes.

Why it matters

CVE-2026-76294 allows unauthorized changes to field extractions and transformations in Splunk Enterprise. Defenders should prioritize verifying and upgrading to patched versions, restricting access, and monitoring for unauthorized changes.

  • Potential unauthorized changes to field extractions and transformations
  • Need to verify and upgrade to patched versions
  • Requirement to restrict access to field extraction management

Technical summary

The vulnerability exists in Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16. A user without 'admin' or 'power' roles can move field extractions or transformations to apps they do not have read access to, due to insufficient validation of destination app access by the REST API. This issue allows unauthorized changes to field extractions and transformations in Splunk Enterprise. Defenders should prioritize verifying and upgrading to patched versions, restricting access, and monitoring for unauthorized changes.

Defensive priority

Defenders should prioritize verifying and upgrading to patched versions, restricting access to field extraction management, and monitoring for unauthorized changes.

Recommended defensive actions

  • Verify and upgrade Splunk Enterprise to versions 10.4.4, 10.2.8, 10.0.11, or 9.4.16
  • Restrict access to field extraction management to authorized roles
  • Monitor for unauthorized changes to field extractions and transformations
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and Splunk advisory provide details on the vulnerability and affected versions. However, information on potential exploitation or victim organizations is not available. The vulnerability exists in Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16. A user without 'admin' or 'power' roles can move field extractions or transformations to apps they do not have read access to, due to insufficient validation of destination app access by the REST API. Defenders should verify and upgrade to patched versions,

Sources and references

Verified primary and authoritative sources

  • CVE-2026-76294 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-76294

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-76294 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-76294

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.