CVE-2020-37268
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 2% of all known CVEs.
References
Related Vulnerabilities
Other CWE-778 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-7613 | High | 7.5 | 1.3% | - | Fix |
| CVE-2019-19277 | Medium | 6.5 | 1.2% | - | Fix |
| CVE-2019-19295 | Medium | 4.3 | 1.1% | - | - |
| CVE-2022-31120 | Low | 2.1 | 0.9% | - | Fix |
| CVE-2021-43419 | High | 7.5 | 0.7% | - | - |
| CVE-2024-48967 | Critical | 10.0 | 0.6% | - | - |
Common questions
How do I fix CVE-2020-37268?
No published fix for CVE-2020-37268 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2020-37268 being actively exploited?
Not that we know of. CVE-2020-37268 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.12% is the estimated probability that it will be exploited in the next 30 days. That is higher than 2% of all scored CVEs.
How severe is CVE-2020-37268?
CVE-2020-37268 has a CVSS v3 base score of 6.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2020-37268
Markdown
[](https://tridentstack.com/cve/CVE-2020-37268)HTML
<a href="https://tridentstack.com/cve/CVE-2020-37268"><img src="https://tridentstack.com/cve/badge/CVE-2020-37268.svg" alt="CVE-2020-37268"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-25.