The guard checker in Rocq Prover does not follow recursive calls made through a fixpoint's own arguments. A fixpoint may pass itself as a higher-order argument to a second fixpoint, which then applies it to a value that is not a subterm of the structural argument. Passing the recursive function to a plain definition is rejected because the checker unfolds the definition and observes the call, but passing it to a fixpoint is accepted because higher-order recursive calls through fixpoint arguments are not tracked. This admits a type that is definitionally equal to its own negation, so self-application produces False in purely definitional code, without tactics, axioms, plugins or unsafe flags, and Print Assumptions reports the result as closed under the global context. Fixed in Rocq 9.2.0.
CVE-2026-72705
Score 6.3 from GitHub Security Advisory published 2026-08-24. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
August 24, 2026
Last Modified
August 24, 2026
Advisory Details (5)
Auto-updated Aug 24, 2026Rocq Prover before 9.2.0 Guard Checker Accepts Fixpoint Passed as a Higher-Order Argument | Advisories | VulnCheck
https://www.vulncheck.com/advisories/rocq-prover-before-guard-checker-accepts-fixpoint-passed-as-a-higher-order-argumentFix issues with uniform arguments of inner fixpoints in guard condition
Patch available: rocq-prover/rocq V9.3+rc1 (PR #21684 merged 2026-03-04)
https://github.com/rocq-prover/rocq/pull/21684Guard checker soundness bug: higher-order recursive call through fixpoint · Issue #21683 · rocq-prover/rocq · GitHub
https://github.com/rocq-prover/rocq/issues/21683GitHub - rocq-prover/rocq: The Rocq Prover is an interactive theorem prover, or proof assistant. It provides a formal language to write mathematical definitions, executable algorithms and theorems together with an environment for semi-interactive development of machine-checked proofs. · GitHub
https://github.com/rocq-prover/rocqGitHub - endrazine/rocq-cve-poc-21683 · GitHub
https://github.com/endrazine/rocq-cve-poc-21683Vendor Advisories for CVE-2026-72705(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 18:07 UTCEG score recompute
- 2026-08-25 18:06 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 20:25 UTCEG score recompute
- 2026-08-24 20:11 UTCEG score recompute
- 2026-08-24 20:11 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-72705?
When was CVE-2026-72705 disclosed?
Is CVE-2026-72705 actively exploited?
What is the CVSS score of CVE-2026-72705?
How do I remediate CVE-2026-72705?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72705
Is Your Infrastructure Affected by CVE-2026-72705?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.