{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-76285 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76285 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76285 is a critical vulnerability in Splunk Splunk, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76285 and fix it if it is affected.\n\nWhat it is: CVE-2026-76285 is a critical vulnerability in Splunk Splunk, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76285 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-76285/ (Markdown: https://insights.sbomify.com/CVE-2026-76285/index.md)","id":"CVE-2026-76285","markdown":"https://insights.sbomify.com/CVE-2026-76285/index.md","name":"CVE-2026-76285","record":{"aliases":["GHSA-fw3v-w3rf-g749"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise","requires_auth":"none","summary":"Splunk Enterprise contains vulnerabilities due to improper adherence to coding standards, requiring a software hardening patch.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"splunk","vendor":"splunk"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-710","name":"Improper Adherence to Coding Standards"}],"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-76285 are related to improper adherence to coding standards and are grouped under the Common Weakness Enumeration (CWE) CWE-710.","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":"Improper Adherence to Coding Standards in Splunk Enterprise","id":"CVE-2026-76285","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk"],"type":"other","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Server-Side Request Forgery (SSRF) through Custom API Tools in Splunk MCP Server","id":"CVE-2026-76286"},"packages":[],"prev":{"headline":"Improper Neutralization in Splunk Enterprise","id":"CVE-2026-76284"},"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":"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Splunk"]},"summary":"Splunk Enterprise contains vulnerabilities due to improper adherence to coding standards, requiring a software hardening patch.","url":"https://insights.sbomify.com/CVE-2026-76285/"}