BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-76310High confidence

Improper Access Control through Embedded Report REST API Requests in Splunk Enterprise

Splunk · Splunk Enterprise

9.4CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Mitigation 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-63117

No EUVD known-exploited evidence

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an embedded report token could download the associated search job dispatch archive, recover session material, and use it to access all relevant data available to the report owner and affect system integrity, including by performing administrative actions when the owner holds the "admin" Splunk role. The vulnerability is possible because embedded report access does not block Representational State Transfer (REST) API dispatch archive download requests. For more information see Additional configuration for embedded reports (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/9.1/report-management/additional-configuration-for-embedded-reports) and About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) 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
9.4 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Mitigation available
01

What, why and how

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an embedded report token could download the associated search job dispatch archive, recover session material, and use it to access all relevant data available to the report owner and affect system integrity, including by performing administrative actions when the owner holds the "admin" Splunk role. The vulnerability is possible because embedded report access does not block Representational State Transfer (REST) API dispatch archive download requests. For more information see Additional configuration for embedded reports (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/9.1/report-management/additional-configuration-for-embedded-reports) and About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.

What

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an embedded report token could download the associated search job dispatch archive, recover session material, and use it to access all relevant data available to the report owner and affect system integrity, including by performing administrative actions when the owner holds the "admin" Splunk role. The vulnerability is possible because embedded report access does not block Representational State Transfer (REST) API dispatch archive download requests. For more information see Additional configuration for embedded reports (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/9.1/report-management/additional-configuration-for-embedded-reports) and About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.

Why

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an embedded report token could download the associated search job dispatch archive, recover session material, and use it to access all relevant data available to the report owner and affect system integrity, including by performing administrative actions when the owner holds the "admin" Splunk role. The vulnerability is possible because embedded report access does not block Representational State Transfer (REST) API dispatch archive download requests. For more information see Additional configuration for embedded reports (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/9.1/report-management/additional-configuration-for-embedded-reports) and About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.

Why

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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 Access Control → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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-284 ↗

CWE-284: Improper Access Control. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

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:N/UI:N/S:U/C:H/I:H/A:L

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.PRNonePrivileges required: The attacker does not need an account or existing 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.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedCWE-284
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-63117Official EUVD mapping

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an embedded report token could download the associated search job dispatch archive, recover session material, and use it to access all relevant data available to the report owner and affect system integrity, including by performing administrative actions when the owner holds the "admin" Splunk role. The vulnerability is possible because embedded report access does not block Representational State Transfer (REST) API dispatch archive download requests. For more information see Additional configuration for embedded reports (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/9.1/report-management/additional-configuration-for-embedded-reports) and About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.

Official EUVD record
BSI · German · WID-SEC-W-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-76256 Référence CVE CVE-2026-76257 https://www.cve.org/CVERecord?id=CVE-2026-76257 Référence CVE CVE-2026-76258 https://www.cve.org/CVERecord?id=CVE-2026-76258 Référence CVE CVE-2026-76259 https://www.cve.org/CVERecord?id=CVE-2026-76259 Référence CVE CVE-2026-76260 https://www.cve.org/CVERecord?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=

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

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/SVD-2026-0808 Change log Titolo della tabella Versione Note Data 1.0 Pubblicato il 20-08-2026 20/08/2026 Impatto sistemico Alto (65.89) Argomenti Splunk Splunk Enterprise Splunk SO

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 allowing unauthenticated users with embedded report tokens to download search job archives and access data or perform administrative actions via insufficient REST API restrictions.

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.
Mitigation available
Affected
10.4 < 10.4.2; 10.2 < 10.2.6; 10.0 < 10.0.9; 9.4 < 9.4.14
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Apply the mitigation in the linked authoritative guidance while planning the vendor's permanent fix.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 19 Aug 2026 · Last source change 27 Aug 2026, 16:24 UTC · CWE-284 · Improper Access Control

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-63117
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-63117↗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-76310 · cve.blacktree.nl