{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-76300 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76300 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76300 is a high-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-76300 and fix it if it is affected.\n\nWhat it is: CVE-2026-76300 is a high-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-76300 in the wild and no public exploit code.\n\nAffected product: Splunk Enterprise. 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-76300/ (Markdown: https://insights.sbomify.com/CVE-2026-76300/index.md)","id":"CVE-2026-76300","markdown":"https://insights.sbomify.com/CVE-2026-76300/index.md","name":"CVE-2026-76300","record":{"aliases":["GHSA-g462-7qj6-4f59"],"analysis":null,"analysis_generated_by":null,"assigner":"cisco","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-664","name":"Improper Control of a Resource Through its Lifetime"}],"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-76300 are related to improper control of a resource through its lifetime and are grouped under the Common Weakness Enumeration (CWE) CWE-664.","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":"Security Hardening in Splunk Enterprise - October 2026","id":"CVE-2026-76300","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Security Hardening in Splunk Enterprise - October 2026","id":"CVE-2026-76301"},"packages":[],"prev":{"headline":"Security Hardening in Splunk Enterprise - October 2026","id":"CVE-2026-76299"},"products":["Splunk Enterprise"],"published":"2026-10-21","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":"total"},"state":"PUBLISHED","updated":"2026-10-26","vendors":["Splunk"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-76300/"}