Skip to main content
VulnerabilityPublished Updated

CVE-2026-53432: fzf is vulnerable to Integer Overflow leading to crash in FuzzyMatchV2 function

Affects fzfSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 0.73.1 soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
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.
Patch
Available – fixed in 0.73.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 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

Upgrade github.com/junegunn/fzf to 0.73.1.

Affected software

ProductAffectedFixed in
Gogithub.com/junegunn/fzfpkg:golang/github.com/junegunn/fzfOther threatsAffected
  • <0.73.1
Fixed in
  • 0.73.1

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

AI-suggested

Upgrade fzf to version 0.73.1 or later where this integer overflow vulnerability has been fixed. No other mitigations are indicated.

Description

fzf is vulnerable to Integer Overflow leading to crash in FuzzyMatchV2 function. When input line length is approximately 2,200,000 bytes and pattern length is 999 bytes, the product overflows. The Go runtime detects the invalid slice bounds and terminates the process immediately with a non-recoverable panic. This issue was fixed in version 0.73.1.

References

Community reviews

Loading reviews…