{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-131305 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-131305 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-131305 is a high-severity vulnerability in Splunk AI Assistant, published on 19 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-131305 and fix it if it is affected.\n\nWhat it is: CVE-2026-131305 is a high-severity vulnerability in Splunk AI Assistant, published on 19 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-131305 in the wild and no public exploit code.\n\nAffected product: Splunk AI Assistant. 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-131305/ (Markdown: https://insights.sbomify.com/CVE-2026-131305/index.md)","id":"CVE-2026-131305","markdown":"https://insights.sbomify.com/CVE-2026-131305/index.md","name":"CVE-2026-131305","record":{"aliases":["GHSA-84hp-vf92-h67x"],"analysis":null,"analysis_generated_by":null,"assigner":"cisco","component":null,"cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-15","name":"External Control of System or Configuration Setting"}],"description":"In Splunk AI Assistant versions below 2.0.0, a user who does not hold the \"admin\" or \"power\" Splunk roles could submit client-controlled feature settings through the Representational State Transfer (REST) API. This could modify limited response metadata outside the expected server-side configuration.\nThe vulnerability is possible because the REST API processes client-supplied feature settings without enforcing the expected server-side configuration boundary.","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":"Improper Input Validation through the REST API in Splunk AI Assistant","id":"CVE-2026-131305","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"Tanium addressed an insertion of sensitive information into a log file vulnerability in TanOS.","id":"CVE-2026-131575"},"nickname":null,"packages":[],"prev":{"headline":"Authorization Bypass through the REST API in Splunk AI Assistant","id":"CVE-2026-131304"},"products":["Splunk AI Assistant"],"published":"2026-11-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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","text_fixes":[],"updated":"2026-11-19","vendor_status":[],"vendors":["Splunk"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-131305/"}