# CVE-2020-37268: Coq and Rocq Prover Print Assumptions Omits Unsafe Universe Checking Inlined Through Parameter Inline

> Attackers can bypass audit checks in Coq by hiding unsafe universe operations behind inlined parameters, allowing proofs of false statements to appear valid.

- **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-5fm4-65fg-j439

## What is CVE-2020-37268?

CVE-2020-37268 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

Print Assumptions does not report that a definition was produced while universe checking was disabled when that definition reaches the caller through Parameter Inline in a module type. Applying a functor inlines the body of the parameter, and the inlining drops the record that the term was built under Unset Universe Checking, so the resulting constant carries no trace of the unsafe operation. A module implementation can therefore prove False using a universe inconsistency, expose it through an inlined parameter, and have Print Assumptions report the dependent proof as closed under the global context. Because Print Assumptions is the in-process audit used to confirm that a development rests on no unexpected assumptions, a dependency built this way passes that audit while proving arbitrary propositions. The standalone checker coqchk does reject the resulting compiled file. The project records this in dev/doc/critical-bugs.md under non-fixed bugs and rates the risk as moderate when coqchk is not used.

Weakness: CWE-778 (Insufficient Logging)

## Which versions are affected by CVE-2020-37268?


## How do I fix CVE-2020-37268?

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

## Is CVE-2020-37268 being exploited?

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

Public exploit code:

- CVE-2020-37268 — Rocq/Coq Print Assumptions Omits Unsafe Universe Checking via Parameter Inline (github_poc): https://github.com/endrazine/rocq-cve-poc-12155

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37268 and fix it if it is affected.

What it is: CVE-2020-37268 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-2020-37268 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-2020-37268/ (Markdown: https://insights.sbomify.com/CVE-2020-37268/index.md)
```

## Sources

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

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