{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-76366 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76366 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76366 is a medium-severity vulnerability in Splunk SOAR, 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-76366 and fix it if it is affected.\n\nWhat it is: CVE-2026-76366 is a medium-severity vulnerability in Splunk SOAR, 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-76366 in the wild and no public exploit code.\n\nAffected product: Splunk SOAR. 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-76366/ (Markdown: https://insights.sbomify.com/CVE-2026-76366/index.md)","id":"CVE-2026-76366","markdown":"https://insights.sbomify.com/CVE-2026-76366/index.md","name":"CVE-2026-76366","record":{"aliases":["GHSA-24cw-c957-pr32"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk SOAR","requires_auth":"low_privilege","summary":"Authenticated users can exploit REST API filtering to recover session tokens, leading to unauthorized access to all data available to the affected user.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"soar","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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Splunk SOAR versions below 8.6.0, a user with a valid Splunk SOAR account could use Representational State Transfer (REST) API filtering on playbook runs to recover session tokens that compromise all data available to the affected user. The information disclosure is possible because Splunk SOAR does not block REST API filters from matching values that responses otherwise hide. For more information see REST Run Playbook (https://help.splunk.com/en/splunk-soar/soar-cloud/rest-api-reference/run-playbook-endpoints/rest-run-playbook) 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":"Information Disclosure through the REST API in Splunk SOAR","id":"CVE-2026-76366","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Stored Cross-Site Scripting (XSS) through Notes in Splunk SOAR","id":"CVE-2026-76367"},"packages":[],"prev":{"headline":"Structured Query Language (SQL) Injection through Custom Lists in Splunk SOAR","id":"CVE-2026-76365"},"products":["Splunk SOAR"],"published":"2026-08-19","related":[{"cvss_score":8.6,"headline":"Unauthenticated Log Injection In Splunk SOAR","id":"CVE-2023-3997","kev_date_added":null,"published":"2023-07-31"},{"cvss_score":8.1,"headline":"Authentication Bypass through IP Address Spoofing in the Automation Broker in Splunk SOAR","id":"CVE-2026-76356","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":7.6,"headline":"Remote Code Execution (RCE) through Path Traversal in the REST API in Splunk SOAR","id":"CVE-2026-76357","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":7.4,"headline":"Improper Certificate Validation through CyberArk Vault Privileged Access Manager in Splunk SOAR","id":"CVE-2026-76362","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":6.5,"headline":"Path Traversal through App Installation Tar Extraction in Splunk SOAR","id":"CVE-2026-76358","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":6.5,"headline":"Path Traversal through Universal Forwarder Installer Archive Extraction in Splunk SOAR","id":"CVE-2026-76359","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":6.5,"headline":"Structured Query Language Injection through the REST API in Splunk SOAR","id":"CVE-2026-76363","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-08-20","vendors":["Splunk"]},"summary":"Authenticated users can exploit REST API filtering to recover session tokens, leading to unauthorized access to all data available to the affected user.","url":"https://insights.sbomify.com/CVE-2026-76366/"}