ShellCodeX
Tools • Events • News • Insights
SEO Checker
ShellCodeX vulnerability brief
MEDIUM EPSS 0.1% Received

CVE-2020-37268

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.

Published 24 Aug 2026, 20:16 UTC Last modified 25 Aug 2026, 15:16 UTC
SCX

ShellCodeX risk assessment

Planned remediation priority based on exploitation evidence, CVSS conditions and affected-product data.

PriorityEvidenceDecision use
Planned EPSS estimates a 0.10% near-term exploitation probability. Validate against your asset inventory and vendor advisory.
Planned Exploitation does not require prior privileges. Validate against your asset inventory and vendor advisory.
01

Attack profile

The conditions required to exploit this vulnerability and its potential impact.

Attack vector Local
Attack complexity Low
Privileges required None
User interaction Passive
Scope Not assessed
Confidentiality Not assessed
Integrity Not assessed
Availability Not assessed
02

Affected products

Product applicability statements supplied with the NVD record.

NVD has not published structured affected-product data for this record.
03

Weakness classification

CWE categories help security teams group the underlying software weakness.

04

Source references

External advisories, patches and technical reports attached to this CVE record.