Rocq Prover through 9.2.0 Guard Checker Trusts Corrupted Recursive Tree After Transport
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Timeline
- 24 Aug 2026, 20:08 UTCPublishedCVE List
- 26 Oct 2026, 00:18 UTCFirst reported exploitedoss-security
- NowNot on CISA's known exploited list yet
Reports 1
One outlet reports exploitation. Reports are not confirmation; each links to its source.
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.
Text from CVE List
Affected versions 1
- rocqaffected: all versions through 9.2.0CVE List
References 5
- github.com/rocq-prover/rocq/pull/22027Fixvia CVE List
- vulncheck.com/advisories/rocq-prover-through-guard-checker-trusts-corrupted-recursive-tree-after-transportAdvisoryvia CVE List
- github.com/endrazine/rocq-cve-poc-22024Exploitvia CVE List
- github.com/rocq-prover/rocqReferencevia CVE List
- github.com/rocq-prover/rocq/issues/22024Referencevia CVE List