{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-20379 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-20379 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-20379 is a low-severity vulnerability in Splunk Splunk, published on 12 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-20379 and fix it if it is affected.\n\nWhat it is: CVE-2025-20379 is a low-severity vulnerability in Splunk Splunk, published on 12 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-20379 in the wild and no public exploit code.\n\nAffected product: Splunk Splunk. 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-2025-20379/ (Markdown: https://insights.sbomify.com/CVE-2025-20379/index.md)","id":"CVE-2025-20379","markdown":"https://insights.sbomify.com/CVE-2025-20379/index.md","name":"CVE-2025-20379","record":{"aliases":["GHSA-3p87-8mrf-82ww"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise","requires_auth":"low_privilege","summary":"Low-privileged users can bypass SPL risky command safeguards via a REST endpoint, executing commands with higher privileges after phishing a victim.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"splunk","vendor":"splunk"},{"product":"splunk_cloud_platform","vendor":"splunk"}],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Splunk Enterprise versions below 10.0.1, 9.4.5, 9.3.7, and 9.2.9 and Splunk Cloud Platform versions below 9.3.2411.116, 9.3.2408.124, 10.0.2503.5 and 10.1.2507.1, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could run a saved search with a risky command using the permissions of a higher-privileged user to bypass the SPL safeguards for risky commands. They could bypass these safeguards on the “/services/streams/search“ endpoint through its “q“ parameter by circumventing endpoint restrictions using character encoding in the REST path. The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated user should not be able to exploit the vulnerability at will.","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":"Security feature bypass in Splunk Cloud Platform","id":"CVE-2025-20379","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk","splunk:splunk_cloud_platform"],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"SPL commands allowlist controls bypass in Splunk MCP Server app through \"run_splunk_query\" MCP tool","id":"CVE-2025-20381"},"packages":[],"prev":{"headline":"Open Redirect on Web Login endpoint in Splunk Enterprise","id":"CVE-2025-20378"},"products":["Splunk Cloud Platform","Splunk Enterprise"],"published":"2025-11-12","related":[{"cvss_score":9.8,"headline":"Splunk Enterprise Missing Authentication for Critical Function","id":"CVE-2026-20253","kev_date_added":"2026-06-18","published":"2026-06-10"},{"cvss_score":9.8,"headline":"Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise","id":"CVE-2026-76268","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":9.8,"headline":"Improper Neutralization in Splunk Enterprise","id":"CVE-2026-76284","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":9.8,"headline":"Improper Adherence to Coding Standards in Splunk Enterprise","id":"CVE-2026-76285","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2017-17067","kev_date_added":null,"published":"2017-11-30"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2016-10126","kev_date_added":null,"published":"2017-01-10"},{"cvss_score":9.4,"headline":"Improper Access Control through Embedded Report REST API Requests in Splunk Enterprise","id":"CVE-2026-76310","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":"2025-11-12","vendors":["Splunk"]},"summary":"Low-privileged users can bypass SPL risky command safeguards via a REST endpoint, executing commands with higher privileges after phishing a victim.","url":"https://insights.sbomify.com/CVE-2025-20379/"}