{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-67846 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-67846 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67846 is a high-severity vulnerability in n/a, published on 18 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-67846 and fix it if it is affected.\n\nWhat it is: CVE-2026-67846 is a high-severity vulnerability in n/a, published on 18 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-67846 in the wild and no public exploit code.\n\nAffected product: n/a. 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-67846/ (Markdown: https://insights.sbomify.com/CVE-2026-67846/index.md)","id":"CVE-2026-67846","markdown":"https://insights.sbomify.com/CVE-2026-67846/index.md","name":"CVE-2026-67846","record":{"aliases":["GHSA-5x2c-mgv4-rwhh"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RISC-V processor core","requires_auth":"low_privilege","summary":"Incorrect privilege assignment in BOOM processor TLB allows privilege escalation due to missing mode validity checks.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"Berkeley Out-of-Order Machine (BOOM) commit 5223e44cfeb26f41380057a2eb4d651197475f69 contains a potential incorrect privilege assignment issue in the v3 and v4 NBDTLB implementations. The raw mstatus.SUM value participates in the read and write permission logic without an explicit local satp.MODE validity check at the use site","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Privilege escalation in n/a","id":"CVE-2026-67846","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"SQL injection in n/a","id":"CVE-2026-67854"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2026-67827"},"products":["n/a"],"published":"2026-08-18","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-08-21","vendors":["n/a"]},"summary":"Incorrect privilege assignment in BOOM processor TLB allows privilege escalation due to missing mode validity checks.","url":"https://insights.sbomify.com/CVE-2026-67846/"}