{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-29644 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-29644 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-29644 is a medium-severity vulnerability in n/a, published on 21 Apr 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-29644 and fix it if it is affected.\n\nWhat it is: CVE-2026-29644 is a medium-severity vulnerability in n/a, published on 21 Apr 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-29644 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-29644/ (Markdown: https://insights.sbomify.com/CVE-2026-29644/index.md)","id":"CVE-2026-29644","markdown":"https://insights.sbomify.com/CVE-2026-29644/index.md","name":"CVE-2026-29644","record":{"aliases":["GHSA-p2hj-qw82-grpc"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RISC-V processor","requires_auth":"low_privilege","summary":"Local attackers can tamper with Physical Memory Attribute settings in XiangShan processors, potentially leading to privilege escalation or information disclosure.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"XiangShan (open-source high-performance RISC-V processor) commit edb1dfaf7d290ae99724594507dc46c2c2125384 (2024-11-28) has improper gating of its distributed CSR write-enable path, allowing illegal CSR write attempts to alter custom PMA (Physical Memory Attribute) CSR state. Though the RISC-V privileged specification requires an illegal-instruction exception for non-existent/illegal CSR accesses, affected XiangShan versions may still propagate such writes to replicated PMA configuration state. Local attackers able to execute code on the core (privilege context depends on system integration) can exploit this to tamper with memory-attribute enforcement, potentially leading to privilege escalation, information disclosure, or denial of service depending on how PMA enforces platform security and isolation boundaries.","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-29644","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Other in n/a","id":"CVE-2026-29645"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2026-29643"},"products":["n/a"],"published":"2026-04-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":"partial"},"state":"PUBLISHED","updated":"2026-04-21","vendors":["n/a"]},"summary":"Local attackers can tamper with Physical Memory Attribute settings in XiangShan processors, potentially leading to privilege escalation or information disclosure.","url":"https://insights.sbomify.com/CVE-2026-29644/"}