Proof-integrity compromise via unchecked recursive-tree transport
Published Aug 24, 2026 · Updated Aug 25, 2026
Improper guard checking in Rocq Prover 9.2.0 and earlier allows local users to compromise proof integrity via crafted fixpoints. The guard checker preserves an inductive type across transport but fails to recheck its altered recursive tree, so a nested fixpoint is accepted as decreasing. Exploitation requires processing a proof that uses univalence-consistent axioms and yields False, allowing any proposition to follow.
Summary
What happened
Improper guard checking in Rocq Prover 9.2.0 and earlier allows local users to compromise proof integrity via crafted fixpoints. The guard checker preserves an inductive type across transport but fails to recheck its altered recursive tree, so a nested fixpoint is accepted as decreasing. Exploitation requires processing a proof that uses univalence-consistent axioms and yields False, allowing any proposition to follow.
The record
- CVE
- CVE-2026-72704
- Published
- Aug 24, 2026
- Updated
- Aug 25, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-670
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- rocq-cve-poc-22024proof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo