description: "CVE-2026-76397 is a High (8.1) vulnerability: In Splunk AI Toolkit versions below 6.0.0, a user who holds the 'power' Splunk role could…. This entry ships a detection-only PoC a..." keywords: "CVE-2026-76397, CVE-2026-76397 detection, CVE-2026-76397 poc, In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could…"
CVE-2026-76397 — In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could…¶
Key facts
CVE-2026-76397 is a High (8.1) vulnerability: In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could…. This entry ships a detection-only PoC and a Docker test lab.
| CVE | CVE-2026-76397 |
| Severity | High (8.1) |
| Detection / prevention | — |
| PoC | poc.py |
| Source | 2026/CVE-2026-76397/ |
Details¶
English | 한국어
Description¶
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.
Vulnerability Details¶
| Property | Value |
|---|---|
| CVE ID | CVE-2026-76397 |
| Type | IDOR |
| CVSS Score | 8.1 |
Proof of Concept¶
Download¶
# Download PoC script
curl -O https://raw.githubusercontent.com/fankh/vulnerability-poc/main/2026/CVE-2026-76397/poc.py
Usage¶
# Run PoC against target
python3 poc.py --target <TARGET_URL>
# With authentication
python3 poc.py --target <TARGET_URL> --username <USER> --password <PASS>
⚠️ Warning: This PoC is for authorized security testing only. It uses detection-only techniques and does not exploit or damage target systems.
Test Lab¶
This repository includes a Docker-based test environment with both vulnerable and patched applications.
Quick Start¶
# Clone and navigate to CVE directory
cd CVE-2026-76397
# Start both applications
docker-compose up -d
# Run tests
./run-tests.sh # Linux/Mac
./run-tests.ps1 # Windows PowerShell
Application Endpoints¶
| Application | URL | Status |
|---|---|---|
| Vulnerable App | http://localhost:8080 | Shows vulnerability |
| Patched App | http://localhost:8081 | Demonstrates fix |
Directory Structure¶
├── README.md # English documentation
├── README_KO.md # Korean documentation
├── poc.py # PoC detection script
├── docker-compose.yml # Container orchestration
├── run-tests.sh # Linux/Mac test runner
├── run-tests.ps1 # Windows test runner
├── vulnerable-app/ # Vulnerable version
│ ├── app.py
│ ├── Dockerfile
│ └── requirements.txt
└── patched-app/ # Fixed version
├── app.py
├── Dockerfile
└── requirements.txt
References¶
- https://advisory.splunk.com/advisories/SVD-2026-0808
Generated by PoC Generator on 2026-08-23T12:08:03.438324356
Frequently asked questions¶
What is CVE-2026-76397?¶
CVE-2026-76397 is a High (8.1) vulnerability: In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could…. This entry ships a detection-only PoC and a Docker test lab.
How do I detect CVE-2026-76397?¶
Run the detection-only PoC included with this entry against your Docker test lab to confirm whether a target is affected; pair it with your own IDS logging.
How do I block or mitigate CVE-2026-76397?¶
Upgrade to a fixed version per the vendor advisory; the NVD record lists the affected versions. Use the included PoC to verify your remediation.
For authorized security testing and research only. See the full source and NVD record.