hex_to_binary · Heap-based Buffer Overflow
Source GCVE Database
Not known to be exploited · CVSS 9.8 Critical.
Data as of 27 Oct 2026, 00:45 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
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 |
|---|---|---|
GitHubhashcat/hashcatpkg:github/hashcat/hashcatOther 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
Until an official fix is available, avoid processing untrusted PKZIP hash files with hashcat v7.1.2. Monitor vendor channels for updates and apply patches promptly once released.
Description
A heap-based buffer overflow vulnerability exists in the hex_to_binary function of the PKZIP hash parser in hashcat version 7.1.2. This flaw allows an attacker to cause denial of service or potentially execute arbitrary code by providing a specially crafted PKZIP hash file. The vulnerability affects several hashcat modules (17200, 17210, 17220, 17225, and 17230) and is triggered when attacker-controlled hex data is decoded into a fixed-size buffer without proper input-length validation.