CVE-2026-72705

Published: Ago 24, 2026 Last Modified: Ago 24, 2026
ExploitDB:
Other exploit source:
Google Dorks:
MEDIUM 6,8
Attack Vector: local
Attack Complexity: low
Privileges Required: none
User Interaction: passive
Confidentiality: N/A
Integrity: N/A
Availability: N/A
MEDIUM 6,3
Attack Vector: local
Attack Complexity: low
Privileges Required: none
User Interaction: required
Scope: changed
Confidentiality: none
Integrity: high
Availability: none

Description

AI Translation Available

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.

670

Always-Incorrect Control Flow Implementation

Draft
Common Consequences
Security Scopes Affected:
Other
Potential Impacts:
Other Alter Execution Logic
Applicable Platforms
All platforms may be affected
View CWE Details
https://github.com/endrazine/rocq-cve-poc-21683
https://github.com/rocq-prover/rocq
https://github.com/rocq-prover/rocq/issues/21683
https://github.com/rocq-prover/rocq/pull/21684
https://www.vulncheck.com/advisories/rocq-prover-before-guard-checker-accepts-f…