{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-76394 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76394 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76394 is a high-severity missing authorization vulnerability in Splunk AI Toolkit, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76394 and fix it if it is affected.\n\nWhat it is: CVE-2026-76394 is a high-severity missing authorization vulnerability in Splunk AI Toolkit, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76394 in the wild and no public exploit code.\n\nAffected product: Splunk AI Toolkit. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-76394/ (Markdown: https://insights.sbomify.com/CVE-2026-76394/index.md)","id":"CVE-2026-76394","markdown":"https://insights.sbomify.com/CVE-2026-76394/index.md","name":"CVE-2026-76394","record":{"aliases":["GHSA-6w69-87j9-3r87"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk AI Toolkit","requires_auth":"low_privilege","summary":"Low-privileged users can manage containers and modify connection data via the REST API due to missing authorization checks in Splunk AI Toolkit.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"ai_toolkit","vendor":"splunk"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"In Splunk AI Toolkit versions below 6.0.0, a low-privileged user who does not hold the \"admin\" or \"power\" Splunk roles could start, stop, and configure containers, and read or modify connection and configuration data through the Representational State Transfer (REST) API. The missing authorization is possible because multiple REST API handlers in Splunk AI Toolkit do not enforce authorization checks. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing Authorization in Container and Connection Management through the REST API in Splunk AI Toolkit","id":"CVE-2026-76394","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Deserialization in Splunk AI Toolkit","id":"CVE-2026-76395"},"packages":[],"prev":{"headline":"Race Condition during Model Upload through the REST API in Splunk AI Toolkit","id":"CVE-2026-76393"},"products":["Splunk AI Toolkit"],"published":"2026-08-19","related":[{"cvss_score":9.1,"headline":"OS Command Injection in the btool Configuration Helper in Splunk AI Toolkit","id":"CVE-2026-20266","kev_date_added":null,"published":"2026-06-17"},{"cvss_score":8.8,"headline":"Deserialization in Splunk AI Toolkit","id":"CVE-2026-76395","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":8.3,"headline":"Improper Privilege Management through Agent Run History in Splunk AI Toolkit","id":"CVE-2026-76391","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":8.1,"headline":"Improper Access Control in Experiment History through the REST API in Splunk AI Toolkit","id":"CVE-2026-76397","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":8.1,"headline":"Incorrect Permission Assignment for Scheduled Searches in Splunk AI Toolkit","id":"CVE-2026-76399","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":7.5,"headline":"Improper Access Control through Scheduled Searches in Splunk AI Toolkit","id":"CVE-2026-76396","kev_date_added":null,"published":"2026-08-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["Splunk"]},"summary":"Low-privileged users can manage containers and modify connection data via the REST API due to missing authorization checks in Splunk AI Toolkit.","url":"https://insights.sbomify.com/CVE-2026-76394/"}