{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-20238 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-20238 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-20238 is a medium-severity missing authorization vulnerability in Splunk AI Toolkit, published on 20 May 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-20238 and fix it if it is affected.\n\nWhat it is: CVE-2026-20238 is a medium-severity missing authorization vulnerability in Splunk AI Toolkit, published on 20 May 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-20238 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-20238/ (Markdown: https://insights.sbomify.com/CVE-2026-20238/index.md)","id":"CVE-2026-20238","markdown":"https://insights.sbomify.com/CVE-2026-20238/index.md","name":"CVE-2026-20238","record":{"aliases":["GHSA-7rq8-f887-2r5g"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk AI Toolkit","requires_auth":"low_privilege","summary":"Low-privileged users can access confidential data restricted by search filters due to improper role inheritance 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":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"In Splunk AI Toolkit versions below 5.7.3, a low-privileged user that does not hold the 'admin' or 'power' roles could access confidential data that was restricted through `srchFilter` configurations on custom roles.\u003cbr\u003e\u003cbr\u003eThe app contains an `authorize.conf` configuration file with a `srchFilter` entry that modifies the built-in ‘user’ role. Because the Splunk platform combines inherited search filters with the `OR` SPL operator, the injected filter overrides more restrictive filters on child roles.","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 Access Control through Role Inheritance in Splunk AI Toolkit app","id":"CVE-2026-20238","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":"Sensitive Information Disclosure through Log Files in Splunk Enterprise","id":"CVE-2026-20239"},"packages":[],"prev":{"headline":"Cisco Identity Services Engine Hardening Release - Input Validation Vulnerabilities","id":"CVE-2026-20237"},"products":["Splunk AI Toolkit"],"published":"2026-05-20","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.3,"headline":"Missing Authorization in Container and Connection Management through the REST API in Splunk AI Toolkit","id":"CVE-2026-76394","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":"partial"},"state":"PUBLISHED","updated":"2026-05-20","vendors":["Splunk"]},"summary":"Low-privileged users can access confidential data restricted by search filters due to improper role inheritance in Splunk AI Toolkit.","url":"https://insights.sbomify.com/CVE-2026-20238/"}