Skip to main content
CVE-2026-2644VulnerabilityPublished Updated

CVE-2026-2644: niklasso minisat · Out-of-Bounds Read

Affects niklasso minisatSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
niklassominisatAffected
  • =2.0
  • =2.1
  • =2.2.0
Fixed in–

AI-suggested

To mitigate CVE-2026-2644, organizations should first identify all instances of minisat versions 2.0 through 2.2.0 deployed locally. 2) Employ operating system-level sandboxing or containerization to limit minisat's access to memory and system resources, reducing potential damage from exploitation. 3) Monitor local system logs and behavior for anomalies indicative of attempts to exploit this vulnerability. 4) If feasible, review and modify minisat source code to add bounds checking on the variable index parameter in Solver::value, preventing out-of-bounds reads. 5) Engage with the minisat project or community to track patch releases or mitigations. 6) For critical environments, consider replacing minisat with alternative SAT solvers that have no known vulnerabilities. 7) Implement strict privilege separation and access controls to prevent unauthorized local code execution. These targeted mitigations go beyond generic advice by focusing on local access control, code review, and containment strategies.

Description

A weakness has been identified in niklasso minisat up to 2.2.0. This issue affects the function Solver::value in the library core/SolverTypes.h of the component DIMACS File Parser. This manipulation of the argument variable index with the input 2147483648 causes out-of-bounds read. The attack needs to be launched locally. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

References

Community reviews

Loading reviews…