Proof audit bypass via dropped unsafe marker
Published Aug 24, 2026 · Updated Aug 25, 2026
Integrity failure in Rocq Prover 8.11 through 9.2.0 allows attackers to conceal inconsistent proofs through local project input. Functor application inlines a Parameter Inline body but drops the marker showing that its definition was built under Unset Universe Checking. A malicious dependency can therefore prove False yet make Print Assumptions report the proof as closed; exposure requires consuming the dependency and not separately checking its compiled file.
Summary
What happened
Integrity failure in Rocq Prover 8.11 through 9.2.0 allows attackers to conceal inconsistent proofs through local project input. Functor application inlines a Parameter Inline body but drops the marker showing that its definition was built under Unset Universe Checking. A malicious dependency can therefore prove False yet make Print Assumptions report the proof as closed; exposure requires consuming the dependency and not separately checking its compiled file.
The record
- CVE
- CVE-2020-37268
- Published
- Aug 24, 2026
- Updated
- Aug 25, 2026
- Vendor
- Rocq Prover
- Product
- Rocq Prover
- Classifications
- CWE-778, T1195.001
- 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.11 <=9.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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-12155proof of concept · unverified
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