Skip to main content
VulnerabilityPublished

CVE-2026-96780: patorjk figlet.js · Infinite Loop

Affects patorjk figlet.jsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 1.11.3 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.11.3
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 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 15 Nov 2026.

What to do

Upgrade patorjk figlet.js to 1.11.3.

Affected software

ProductAffectedFixed in
patorjkfiglet.jsAffected
  • <1.11.3
Fixed in
  • 1.11.3
npmfiglet.jspkg:npm/figlet.jsOther threatsAffected
  • <1.11.3
Fixed in
  • 1.11.3

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

AI-suggested

Upgrade figlet.js to version 1.11.3 or later, where this infinite loop vulnerability is fixed. No other mitigations are necessary as the issue is resolved in the official patch.

Description

figlet.js versions prior to 1.11.3 contain a vulnerability where the text() and textSync() functions can enter an infinite loop if the whitespaceBreak option is enabled and the specified width is smaller than the width of a single FIGlet character. This occurs because the breakWord() function fails to find a valid break point and does not consume any input, causing generateFigTextLines() to repeatedly process the same input, leading to high CPU usage and memory growth. This issue is resolved in version 1.11.3.

References

Community reviews

Loading reviews…