# CVE-2026-72714: Rocq Prover through 9.2.0 Universe Checking State Desynchronised After Module Close

> Attackers can exploit a state desynchronization in Rocq Prover to prove False, bypassing logical consistency checks and potentially executing arbitrary code.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-95gm-3748-rx8v

## What is CVE-2026-72714?

CVE-2026-72714 is a medium-severity vulnerability in rocq-prover rocq, published on 24 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Rocq Prover does not restore the universe graph's copy of the universe checking flag when a module that locally disabled the check is closed. Local Unset Universe Checking inside a module is expected to last only until the module ends, and the global flag is restored, but the universe graph keeps its own copy which is left disabled. The two views then disagree: Test Universe Checking reports the check as enabled while the kernel continues to accept universe-inconsistent terms. With the constraint between two universes no longer enforced, Hurkens' paradox applies and yields a proof of False, from which any proposition follows. The proof uses no axioms, plugins or unsafe features once the module has closed, and Print Assumptions reports it as closed under the global context, so neither the assumption audit nor the flag query reflects the actual kernel state. No fix is available.

Weakness: CWE-459 (Incomplete Cleanup)

## Which versions are affected by CVE-2026-72714?


## How do I fix CVE-2026-72714?

No fix has been published for CVE-2026-72714 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72714 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72714 exists.

Public exploit code:

- CVE-2026-72714 — Rocq Universe Checking State Desynchronised After Module Close (github_poc): https://github.com/endrazine/rocq-cve-poc-22287

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72714 and fix it if it is affected.

What it is: CVE-2026-72714 is a medium-severity vulnerability in rocq-prover rocq, published on 24 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72714 exists.

Affected product: rocq-prover rocq. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72714/ (Markdown: https://insights.sbomify.com/CVE-2026-72714/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72714
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72714
- OSV: https://osv.dev/vulnerability/CVE-2026-72714

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72714/
Summaries are generated and may contain mistakes; the official description above is the record.