{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-76384 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76384 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76384 is a medium-severity vulnerability in Splunk Attack Analyzer Connector for 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-76384 and fix it if it is affected.\n\nWhat it is: CVE-2026-76384 is a medium-severity vulnerability in Splunk Attack Analyzer Connector for 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-76384 in the wild and no public exploit code.\n\nAffected product: Splunk Attack Analyzer Connector for 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-76384/ (Markdown: https://insights.sbomify.com/CVE-2026-76384/index.md)","id":"CVE-2026-76384","markdown":"https://insights.sbomify.com/CVE-2026-76384/index.md","name":"CVE-2026-76384","record":{"aliases":["GHSA-6cqf-6324-39pj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk SOAR connector","requires_auth":"low_privilege","summary":"Users with action permissions can view sensitive archive passwords in cleartext due to unmasked parameters in the Splunk Attack Analyzer Connector.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"In versions below 2.2.1 of the Splunk Attack Analyzer Connector for Splunk SOAR, a user who holds a role with permission to run actions could expose a sensitive archive password by invoking either the detonate file or detonate url action, because the action's archive_password parameter is not masked and is shown in cleartext in the user interface. The information disclosure is possible because the app does not mark the affected action parameter as a password. For more information see Run an action in Splunk SOAR (https://help.splunk.com/en/splunk-soar/soar-on-premises/use-splunk-soar-on-premises/8.6.0/use-the-command-line-interface-to-perform-tasks-in-splunk-soar-on-premises/run-an-action-in-splunk-soar-on-premises).","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 Action Parameters in Splunk Attack Analyzer Connector for Splunk SOAR","id":"CVE-2026-76384","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":"Information Disclosure through Action Parameters in Venafi app for Splunk SOAR","id":"CVE-2026-76385"},"packages":[],"prev":{"headline":"Information Disclosure through Action Parameters in RSA SecurID Authentication Manager app for Splunk SOAR","id":"CVE-2026-76383"},"products":["Splunk Attack Analyzer Connector for Splunk SOAR"],"published":"2026-08-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":"partial"},"state":"PUBLISHED","updated":"2026-08-20","vendors":["Splunk"]},"summary":"Users with action permissions can view sensitive archive passwords in cleartext due to unmasked parameters in the Splunk Attack Analyzer Connector.","url":"https://insights.sbomify.com/CVE-2026-76384/"}