{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72704 exists.","fix":"No fix has been published for CVE-2026-72704 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-72704 is a medium-severity vulnerability in rocq-prover rocq, published on 24 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-72704 and fix it if it is affected.\n\nWhat it is: CVE-2026-72704 is a medium-severity vulnerability in rocq-prover rocq, published on 24 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72704 exists.\n\nAffected product: rocq-prover rocq. 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-72704/ (Markdown: https://insights.sbomify.com/CVE-2026-72704/index.md)","id":"CVE-2026-72704","markdown":"https://insights.sbomify.com/CVE-2026-72704/index.md","name":"CVE-2026-72704","record":{"aliases":["GHSA-h294-vvmw-mqg3"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Formal proof assistant","requires_auth":"none","summary":"Attackers can exploit a guard checker flaw in Rocq Prover to prove False, enabling arbitrary code execution or logical contradictions in verified software.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"}],"description":"The guard checker in Rocq Prover does not recheck the recursive tree representation of an inductive type parameter after that parameter has been changed by transport. A fixpoint may apply a rewrite along an equality between types to its recursive argument, which the guard checker accepts because the inductive type is preserved, while the recursive tree recorded for the parameter is altered. A second fixpoint that calls the first inherits the altered recursive tree without verification, so a call that is not structurally decreasing is accepted as terminating. The resulting non-terminating definition proves that a natural number equals its own successor and therefore False, from which any proposition follows. The demonstration uses two axioms that follow from univalence and are consistent with the calculus of inductive constructions, so the contradiction comes from the guard check rather than from the assumptions. A fix is proposed but not merged.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-08-23","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-23T23:28:13Z","kind":"github_poc","ref":"https://github.com/endrazine/rocq-cve-poc-22024","stars":0,"title":"CVE-2026-72704 — Rocq Guard Checker Trusts Corrupted Recursive Tree After Transport"}],"tier":"weaponised"},"has_fix":false,"headline":"Rocq Prover through 9.2.0 Guard Checker Trusts Corrupted Recursive Tree After Transport","id":"CVE-2026-72704","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Rocq Prover before 9.2.0 Guard Checker Accepts Fixpoint Passed as a Higher-Order Argument","id":"CVE-2026-72705"},"packages":[],"prev":{"headline":"Rocq Prover 8.20 before 9.2.0 Guard Checker Accepts Non-Terminating Fixpoint via Unchecked Cross-Calls","id":"CVE-2026-72703"},"products":["rocq"],"published":"2026-08-24","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-26","vendors":["rocq-prover"]},"summary":"Attackers can exploit a guard checker flaw in Rocq Prover to prove False, enabling arbitrary code execution or logical contradictions in verified software.","url":"https://insights.sbomify.com/CVE-2026-72704/"}