Skip to main content
VulnerabilityPublished

CVE-2026-3257: TOKUHIROM UnQLite · Dependency on Vulnerable Third-Party Component

Affects TOKUHIROM UnQLiteSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.4% chance of exploitation in 30 days – higher than 36% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
TOKUHIROMUnQLiteAffected
  • <=0.06
Fixed in–
GitHubUnQLitepkg:github/UnQLiteOther threatsAffected
  • <=0.06
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-3257, organizations should first identify all instances of the UnQLite Perl module version 0.06 or earlier in their environments. Since no official patches are currently available, consider the following specific actions: 1) Upgrade to a newer version of the UnQLite Perl module that embeds an updated, secure version of the UnQLite library once released. 2) If an upgrade is not immediately possible, isolate affected applications from untrusted inputs and networks to reduce exposure. 3) Employ runtime protections such as heap overflow detection and memory corruption prevention tools (e.g., AddressSanitizer, DEP, ASLR) to mitigate exploitation risk. 4) Conduct thorough code reviews and penetration testing focusing on areas interacting with the UnQLite module to detect potential exploitation attempts. 5) Monitor security advisories from TOKUHIROM and CPAN for updates or patches. 6) Consider replacing UnQLite with alternative embedded databases that have active maintenance and security support if the risk is unacceptable. 7) Implement strict input validation and sanitization to minimize the chance of triggering the overflow condition. These targeted measures go beyond generic advice and address the specific nature of this dependency vulnerability.

Description

UnQLite versions through 0.06 for Perl uses a potentially insecure version of the UnQLite library. UnQLite for Perl embeds the UnQLite library. Version 0.06 and earlier of the Perl module uses a version of the library from 2014 that may be vulnerable to a heap-based overflow.

References

Community reviews

Loading reviews…