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

Improper Access Control in Experiment History through the REST API in Splunk AI Toolkit

Splunk · Splunk AI Toolkit

8.1HighCVSS 3.1
Recommended action
Within 7 days

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

Fix not verified
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-62962

No EUVD known-exploited evidence

In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) 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.1 · 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.

Fix not verified
01

What, why and how

In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation.

What

In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation.

Why

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation.

Why

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

How

An attacker operating through a network path may attempt exploitation with low privileges. 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 → Authorization Bypass Through User-Controlled Key → cause the confidentiality, integrity or availability impact described by the vendor
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-639 ↗

CWE-639: Authorization Bypass Through User-Controlled Key. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

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:N

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.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-639
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-62962Official EUVD mapping

In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation.

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

d?id=CVE-2026-76388 Référence CVE CVE-2026-76389 https://www.cve.org/CVERecord?id=CVE-2026-76389 Référence CVE CVE-2026-76390 https://www.cve.org/CVERecord?id=CVE-2026-76390 Référence CVE CVE-2026-76391 https://www.cve.org/CVERecord?id=CVE-2026-76391 Référence CVE CVE-2026-76392 https://www.cve.org/CVERecord?id=CVE-2026-76392 Référence CVE CVE-2026-76393 https://www.cve.org/CVERecord?id=CVE-2026-76393 Référence CVE CVE-2026-76394 https://www.cve.org/CVERecord?id=CVE-2026-76394 Référence CVE CVE-2026-76395 https://www.cve.org/CVERecord?id=CVE-2026-76395 Référence CVE CVE-2026-76396 https://www.cve.org/CVERecord?id=CVE-2026-76396 Référence CVE CVE-2026-76397 https://www.cve.org/CVERecord?id=CVE-2026-76397 Référence CVE CVE-2026-76398 https://www.cve.org/CVERecord?id=CVE-2026-76398 Référence CVE CVE-2026-76399 https://www.cve.org/CVERecord?id=CVE-2026-76399 Référence CVE CVE-2026-76400 https://www.cve.org/CVERecord?id=CVE-2026-76400 Référence CVE CVE-2026-76401 https://www.cve.org/CVERecord?id=CVE-2026-76401 Référence CVE CVE-2026-76402 https://www.cve.org/CVERecord?id=CVE-2026-76402 Référence CVE CVE-2026-76403 https://www.cve.org/CVERecord?id=CVE-2026-76403 Référence CVE CVE-2026-76404 https://www.cve.org/CVERecord?id=CVE-2026-76404 Référence CVE CVE-2026-76405 https://www.cve.org/CVERecord?id=

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

oni precedenti alla 2.2.7 Cisco Talos Intelligence for Enterprise Security Cloud 1.0.x, versioni precedenti alla 1.0.3 Azioni di mitigazione In linea con le dichiarazioni del vendor, si raccomanda di aggiornare i prodotti vulnerabili seguendo le indicazioni dei bollettini di sicurezza riportati nella sezione Riferimenti. Di seguito sono riportate le sole CVE relative alle vulnerabilità con gravità “critica” e “alta”: CVE (44) Cerca: Tabella CVE CVE POC EXPLOITATION CVE-2026-76404 : apre una nuova finestra - - CVE-2026-76403 : apre una nuova finestra - - CVE-2026-76402 : apre una nuova finestra - - CVE-2026-76399 : apre una nuova finestra - - CVE-2026-76397 : apre una nuova finestra - - CVE-2026-76396 : apre una nuova finestra - - CVE-2026-76395 : apre una nuova finestra - - CVE-2026-76394 : apre una nuova finestra - - CVE-2026-76391 : apre una nuova finestra - - CVE-2026-76389 : apre una nuova finestra - - CVE-2026-76388 : apre una nuova finestra - - CVE-2026-76387 : apre una nuova finestra - - CVE-2026-76362 : apre una nuova finestra - - CVE-2026-76357 : apre una nuova finestra - - CVE-2026-76356 : apre una nuova finestra - - CVE-2026-76355 : apre una nuova finestra - - CVE-2026-76354 : apre una nuova finestra - - CVE-2026-76352 : apre una nuova finestra - - CVE-2026-76351 : apre una nuova fi

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.
Fix not verified
Affected
5.7 < 6.0.0
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
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 20 Aug 2026, 15:26 UTC · CWE-639 · Authorization Bypass Through User-Controlled Key

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-62962
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 vendor advisory.
    Before
    no authoritative guidance recorded
    After
    vendor advisory
    psirt@cisco.com ↗
  2. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2026-62962↗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-76397 · cve.blacktree.nl