CVE-2024-37794: cvc5 · Improper Input Validation
Affects cvc5Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubcvc5/cvc5pkg:github/cvc5/cvc5Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Restrict access to the CVC5 Solver service to trusted networks and authenticated users only, minimizing exposure to untrusted input sources.
- Implement input validation and sanitization at the application or network gateway level to detect and block malformed or suspicious SMT2 input files before they reach the solver.
- Monitor solver logs and system metrics for abnormal crashes, hangs, or resource consumption spikes indicative of exploitation attempts.
- Employ rate limiting and resource quotas to prevent resource exhaustion from repeated malicious inputs.
- If possible, run the solver within isolated environments or containers to limit the impact of crashes on the broader system.
- Stay informed about official patches or updates from the CVC5 development team and apply them promptly once available.
- Consider alternative SMT solvers with robust input validation if immediate patching is not feasible.
- Incorporate fuzz testing and static analysis in development workflows to identify similar input validation issues proactively.
Description
Improper input validation in CVC5 Solver v1.1.3 allows attackers to cause a Denial of Service (DoS) via a crafted SMT2 input file.