{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-20231 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-20231 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-20231 is a high-severity vulnerability in Splunk Splunk, published on 26 Mar 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-20231 and fix it if it is affected.\n\nWhat it is: CVE-2025-20231 is a high-severity vulnerability in Splunk Splunk, published on 26 Mar 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-20231 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-20231/ (Markdown: https://insights.sbomify.com/CVE-2025-20231/index.md)","id":"CVE-2025-20231","markdown":"https://insights.sbomify.com/CVE-2025-20231/index.md","name":"CVE-2025-20231","record":{"aliases":["GHSA-5q93-m8w2-xmp8"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise","requires_auth":"low_privilege","summary":"A low-privileged user can trick a victim into initiating a request to disclose sensitive information via search permissions in Splunk Enterprise.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"splunk","vendor":"splunk"},{"product":"splunk_secure_gateway","vendor":"splunk"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"In Splunk Enterprise versions below 9.4.1, 9.3.3, 9.2.5, and 9.1.8, and versions below 3.8.38 and 3.7.23 of the Splunk Secure Gateway app on Splunk Cloud Platform, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could run a search using the permissions of a higher-privileged user that could lead to disclosure of sensitive information.\u003cbr\u003e\u003cbr\u003eThe vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated low-privileged 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":"Sensitive Information Disclosure in Splunk Secure Gateway App","id":"CVE-2025-20231","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk"],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Risky Command Safeguards Bypass in “/app/search/search“ endpoint through “s“ parameter in Splunk Enterprise","id":"CVE-2025-20232"},"packages":[],"prev":{"headline":"Missing authorization in Splunk Enterprise","id":"CVE-2025-20230"},"products":["Splunk Enterprise","Splunk Secure Gateway"],"published":"2025-03-26","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":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Splunk"]},"summary":"A low-privileged user can trick a victim into initiating a request to disclose sensitive information via search permissions in Splunk Enterprise.","url":"https://insights.sbomify.com/CVE-2025-20231/"}