{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-76405 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76405 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76405 is a medium-severity vulnerability in Splunk On-Call (VictorOps), 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-76405 and fix it if it is affected.\n\nWhat it is: CVE-2026-76405 is a medium-severity vulnerability in Splunk On-Call (VictorOps), 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-76405 in the wild and no public exploit code.\n\nAffected product: Splunk On-Call (VictorOps). 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-76405/ (Markdown: https://insights.sbomify.com/CVE-2026-76405/index.md)","id":"CVE-2026-76405","markdown":"https://insights.sbomify.com/CVE-2026-76405/index.md","name":"CVE-2026-76405","record":{"aliases":["GHSA-9m34-4r95-4c77"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk On-Call app","requires_auth":"low_privilege","summary":"A low-privileged user can read a partially masked API key from the KV Store due to insufficient masking in the Splunk On-Call app.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"on-call","vendor":"splunk"}],"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 Splunk On-Call (VictorOps) app versions below 1.0.43 on Splunkbase, a user who does not hold the \"admin\" or \"power\" Splunk roles could read a partially masked Application Programming Interface (API) key from the App Key Value Store (KV Store). The exposure is possible because the Splunk On-Call (VictorOps) app does not fully mask the API key before storing it in a KV Store collection that the user can read. For more information see About the app key value store (https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/9.2/administer-the-app-key-value-store/about-the-app-key-value-store) 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 Cleartext Storage in the App Key Value Store in the Splunk On-Call (VictorOps) app","id":"CVE-2026-76405","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 REST API Authentication in Splunk SOAR","id":"CVE-2026-76406"},"packages":[],"prev":{"headline":"Remote Code Execution (RCE) through Deserialization of Untrusted Data in Splunk MCP Server app","id":"CVE-2026-76404"},"products":["Splunk On-Call (VictorOps)"],"published":"2026-08-19","related":[],"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":"A low-privileged user can read a partially masked API key from the KV Store due to insufficient masking in the Splunk On-Call app.","url":"https://insights.sbomify.com/CVE-2026-76405/"}