BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-76314High confidence

Remote Code Execution (RCE) through Splunk Web Manager Configuration in Splunk Enterprise

Splunk · Splunk Enterprise

8.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-63121

No EUVD known-exploited evidence

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who does not hold the "admin" or "power" Splunk roles could perform Remote Code Execution (RCE) by submitting crafted Splunk Web Manager Configuration content. The user could then access all relevant data and affect system integrity and availability. The vulnerability is possible because Splunk Web evaluates manager Extensible Markup Language expressions without sufficient input restrictions, and the associated configuration route does not require the capability expected for manager configuration changes. For more information see About configuration files (https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/10.4/administer-splunk-enterprise-with-configuration-files/about-configuration-files) in the Splunk documentation.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
8.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who does not hold the "admin" or "power" Splunk roles could perform Remote Code Execution (RCE) by submitting crafted Splunk Web Manager Configuration content. The user could then access all relevant data and affect system integrity and availability. The vulnerability is possible because Splunk Web evaluates manager Extensible Markup Language expressions without sufficient input restrictions, and the associated configuration route does not require the capability expected for manager configuration changes. For more information see About configuration files (https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/10.4/administer-splunk-enterprise-with-configuration-files/about-configuration-files) in the Splunk documentation.

What

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who does not hold the "admin" or "power" Splunk roles could perform Remote Code Execution (RCE) by submitting crafted Splunk Web Manager Configuration content. The user could then access all relevant data and affect system integrity and availability. The vulnerability is possible because Splunk Web evaluates manager Extensible Markup Language expressions without sufficient input restrictions, and the associated configuration route does not require the capability expected for manager configuration changes. For more information see About configuration files (https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/10.4/administer-splunk-enterprise-with-configuration-files/about-configuration-files) in the Splunk documentation.

Why

Untrusted data can cross into a code-evaluation path and be interpreted as executable instructions.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

What

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who does not hold the "admin" or "power" Splunk roles could perform Remote Code Execution (RCE) by submitting crafted Splunk Web Manager Configuration content. The user could then access all relevant data and affect system integrity and availability. The vulnerability is possible because Splunk Web evaluates manager Extensible Markup Language expressions without sufficient input restrictions, and the associated configuration route does not require the capability expected for manager configuration changes. For more information see About configuration files (https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/10.4/administer-splunk-enterprise-with-configuration-files/about-configuration-files) in the Splunk documentation.

Why

Untrusted data can cross into a code-evaluation path and be interpreted as executable instructions.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Control of Generation of Code ('Code Injection') → execute code or commands in the affected security context
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-94 ↗

CWE-94: Improper Control of Generation of Code ('Code Injection'). The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkRemote code executionCWE-94
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-63121Official EUVD mapping

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who does not hold the "admin" or "power" Splunk roles could perform Remote Code Execution (RCE) by submitting crafted Splunk Web Manager Configuration content. The user could then access all relevant data and affect system integrity and availability. The vulnerability is possible because Splunk Web evaluates manager Extensible Markup Language expressions without sufficient input restrictions, and the associated configuration route does not require the capability expected for manager configuration changes. For more information see About configuration files (https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/10.4/administer-splunk-enterprise-with-configuration-files/about-configuration-files) in the Splunk documentation.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2929Splunk Splunk Enterprise: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise ausnutzen, um beliebigen Code auszuführen, Berechtigungen zu erweitern, Sicherheitsmaßnahmen zu umgehen, SQL-Injection-, serverseitige Request-Forgery- und Cross-Site-Scripting-Angriffe durchzuführen, sensible Informationen offenzulegen oder zu manipulieren, Denial-of-Service-Zustände auszulösen oder andere, nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1056Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2026-76260 Référence CVE CVE-2026-76261 https://www.cve.org/CVERecord?id=CVE-2026-76261 Référence CVE CVE-2026-76262 https://www.cve.org/CVERecord?id=CVE-2026-76262 Référence CVE CVE-2026-76263 https://www.cve.org/CVERecord?id=CVE-2026-76263 Référence CVE CVE-2026-76309 https://www.cve.org/CVERecord?id=CVE-2026-76309 Référence CVE CVE-2026-76310 https://www.cve.org/CVERecord?id=CVE-2026-76310 Référence CVE CVE-2026-76311 https://www.cve.org/CVERecord?id=CVE-2026-76311 Référence CVE CVE-2026-76312 https://www.cve.org/CVERecord?id=CVE-2026-76312 Référence CVE CVE-2026-76313 https://www.cve.org/CVERecord?id=CVE-2026-76313 Référence CVE CVE-2026-76314 https://www.cve.org/CVERecord?id=CVE-2026-76314 Référence CVE CVE-2026-76315 https://www.cve.org/CVERecord?id=CVE-2026-76315 Référence CVE CVE-2026-76316 https://www.cve.org/CVERecord?id=CVE-2026-76316 Référence CVE CVE-2026-76317 https://www.cve.org/CVERecord?id=CVE-2026-76317 Référence CVE CVE-2026-76318 https://www.cve.org/CVERecord?id=CVE-2026-76318 Référence CVE CVE-2026-76319 https://www.cve.org/CVERecord?id=CVE-2026-76319 Référence CVE CVE-2026-76320 https://www.cve.org/CVERecord?id=CVE-2026-76320 Référence CVE CVE-2026-76321 https://www.cve.org/CVERecord?id=CVE-2026-76321 Référence CVE CVE-2026-76322 https://www.cve.org/CVERecord?id=

Official advisory ↗
CSIRT Italia · Italian · vulnerabilita-in-prodotti-splunk-5Vulnerabilità in prodotti Splunk

nuova finestra - - CVE-2026-76344 : apre una nuova finestra - - CVE-2026-76338 : apre una nuova finestra - - CVE-2026-76336 : apre una nuova finestra - - CVE-2026-76335 : apre una nuova finestra - - CVE-2026-76333 : apre una nuova finestra - - CVE-2026-76332 : apre una nuova finestra - - CVE-2026-76331 : apre una nuova finestra - - CVE-2026-76330 : apre una nuova finestra - - CVE-2026-76325 : apre una nuova finestra - - CVE-2026-76321 : apre una nuova finestra - - CVE-2026-76319 : apre una nuova finestra - - CVE-2026-76317 : apre una nuova finestra - - CVE-2026-76316 : apre una nuova finestra - - CVE-2026-76315 : apre una nuova finestra - - CVE-2026-76314 : apre una nuova finestra - - CVE-2026-76313 : apre una nuova finestra - - CVE-2026-76312 : apre una nuova finestra - - CVE-2026-76311 : apre una nuova finestra - - CVE-2026-76310 : apre una nuova finestra - - CVE-2026-76262 : apre una nuova finestra - - CVE-2026-76259 : apre una nuova finestra - - CVE-2026-76254 : apre una nuova finestra - - CVE-2026-76253 : apre una nuova finestra - - CVE-2026-76251 : apre una nuova finestra - - Riferimenti (4) https://advisory.splunk.com/advisories/SVD-2026-0801 https://advisory.splunk.com/advisories/SVD-2026-0807 https://advisory.splunk.com/advisories/SVD-2026-0804 https://advisory.splunk.com/advisories/

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-029335Splunkにおけるコードインジェクションの脆弱性

Splunk Enterprise のバージョン 10.4.2 未満、10.2.6 未満、10.0.9 未満、および 9.4.14 未満において、「admin」または「power」の Splunk ロールを持たないユーザーが、細工された Splunk Web マネージャー設定コンテンツを送信することでリモートコード実行（RCE）を行う可能性があります。このユーザーはその後、関連するすべてのデータにアクセスでき、システムの整合性および可用性に影響を及ぼす恐れがあります。この脆弱性は、Splunk Web がマネージャーの拡張マークアップ言語（XML）式を十分な入力制限なく評価し、かつ関連する設定ルートがマネージャー設定の変更に必要な権限を要求しないために発生します。詳細については、Splunk ドキュメントの「設定ファイルについて」（https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/10.4/administer-splunk-enterprise-with-configuration-files/about-configuration-files）をご参照ください。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0322Kwetsbaarheden verholpen in Splunk Enterprise door Splunk

Certain versions of Splunk Enterprise prior to 10.4.2, 10.2.6, 10.0.9, and 9.4.14 contain a vulnerability in Splunk Web Manager Configuration allowing non-admin users to execute remote code due to insufficient input validation and capability checks.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Splunk Enterprise: 10.4 < 10.4.2, 10.2 < 10.2.6, 10.0 < 10.0.9, 9.4 < 9.4.14
Fixed
Upgrade Splunk Enterprise to versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14, or higher.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 19 Aug 2026 · Last source change 27 Aug 2026, 16:24 UTC · CWE-94 · Improper Control of Generation of Code ('Code Injection')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-23
European sourceENISA EUVD · EUVD-2026-63121
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from no authoritative guidance recorded to authoritative remediation link · mitigation.
    Before
    no authoritative guidance recorded
    After
    authoritative remediation link · mitigation
    psirt@cisco.com ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    psirt@cisco.com ↗
  3. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Mitigation reference recorded
ENISA EUVD · EUVD-2026-63121↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-76314 · cve.blacktree.nl