在 Rocq Prover 中,守卫检查器(guard checker)将嵌套相互固定点(nested mutual fixpoint)的参数视为一致的(uniform),而未检查该固定点不同主体(body)之间的调用关系。 中的 函数仅检查自递归调用(self-recursive calls);因此,当没有任何主体调用自身时,该函数会错误地得出结论认为所有参数都是一致的。 若某一参数通过从一个主体到另一个主体的交叉调用(cross-call)而不断增大,则该参数仍保留其从外层固定点继承而来的子项规范(subter
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| rocq-prover | rocq | 8.20 ~ 9.2.0 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-72705 | 6.3 MEDIUM | Rocq Prover before 9.2.0 Guard Checker Accepts Fixpoint Passed as a Higher-Order Argument |
| CVE-2026-72714 | 6.3 MEDIUM | Rocq Prover through 9.2.0 Universe Checking State Desynchronised After Module Close |
| CVE-2026-72704 | 6.3 MEDIUM | Rocq Prover through 9.2.0 Guard Checker Trusts Corrupted Recursive Tree After Transport |
| CVE-2020-37268 | 6.3 MEDIUM | Coq and Rocq Prover Print Assumptions Omits Unsafe Universe Checking Inlined Through Param |
No comments yet