{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-76283 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76283 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76283 is a high-severity vulnerability in Splunk Splunk, published on 7 Oct 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-76283 and fix it if it is affected.\n\nWhat it is: CVE-2026-76283 is a high-severity vulnerability in Splunk Splunk, published on 7 Oct 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-76283 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-2026-76283/ (Markdown: https://insights.sbomify.com/CVE-2026-76283/index.md)","id":"CVE-2026-76283","markdown":"https://insights.sbomify.com/CVE-2026-76283/index.md","name":"CVE-2026-76283","record":{"aliases":["GHSA-8xjr-85h4-xc23"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise","requires_auth":"low_privilege","summary":"Attackers can bypass security protections in Splunk Enterprise due to a protection mechanism failure, requiring a software hardening patch.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"splunk","vendor":"splunk"}],"cvss":{"score":7.6,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-76283 are related to protection mechanism failure and are grouped under the Common Weakness Enumeration (CWE) CWE-693.","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":"Protection Mechanism Failure in Splunk Enterprise","id":"CVE-2026-76283","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk"],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Neutralization in Splunk Enterprise","id":"CVE-2026-76284"},"packages":[],"prev":{"headline":"Improper Control of a Resource Through its Lifetime in Splunk Enterprise","id":"CVE-2026-76282"},"products":["Splunk Enterprise"],"published":"2026-10-07","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":"2026-10-16","vendors":["Splunk"]},"summary":"Attackers can bypass security protections in Splunk Enterprise due to a protection mechanism failure, requiring a software hardening patch.","url":"https://insights.sbomify.com/CVE-2026-76283/"}