{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72703 exists.","fix":"No fix has been published for CVE-2026-72703 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-72703 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-72703 and fix it if it is affected.\n\nWhat it is: CVE-2026-72703 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-72703 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-72703/ (Markdown: https://insights.sbomify.com/CVE-2026-72703/index.md)","id":"CVE-2026-72703","markdown":"https://insights.sbomify.com/CVE-2026-72703/index.md","name":"CVE-2026-72703","record":{"aliases":["GHSA-q4cf-fp8g-gjg9"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rocq Prover","requires_auth":"none","summary":"Attackers can exploit a guard checker flaw in Rocq Prover to prove False, enabling arbitrary code execution via logical inconsistency.","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 treats a parameter of a nested mutual fixpoint as uniform without examining calls between the different bodies of that fixpoint. find_uniform_parameters in kernel/inductive.ml inspects only self-recursive calls, so when no body calls itself the function concludes that every parameter is uniform. A parameter that grows through a cross-call from one body to another therefore keeps the subterm specification it inherited from the enclosing fixpoint, and a recursive call guarded by that specification is accepted although the argument is not structurally smaller. A non-terminating definition is admitted as structurally decreasing, which yields a term whose value equals its own successor and so a proof of False, from which any proposition follows. The proof requires no axioms, plugins or unsafe flags and Print Assumptions reports it as closed under the global context. Introduced in Coq 8.20 and fixed in Rocq 9.2.0.","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:23Z","kind":"github_poc","ref":"https://github.com/endrazine/rocq-cve-poc-21682","stars":0,"title":"CVE-2026-72703 — Rocq Guard Checker Accepts Non-Terminating Fixpoint via Unchecked Cross-Calls"}],"tier":"weaponised"},"has_fix":false,"headline":"Rocq Prover 8.20 before 9.2.0 Guard Checker Accepts Non-Terminating Fixpoint via Unchecked Cross-Calls","id":"CVE-2026-72703","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 through 9.2.0 Guard Checker Trusts Corrupted Recursive Tree After Transport","id":"CVE-2026-72704"},"packages":[],"prev":{"headline":"Grav CMS before 2.0.16 Origin Validation Bypass via Referer","id":"CVE-2026-72702"},"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 via logical inconsistency.","url":"https://insights.sbomify.com/CVE-2026-72703/"}