Categories
CVE-2026-96780

Vulnerability in figlet (CVE-2026-96780)

Summary

Vulnerability in figlet (CVE-2026-96780). Risk of unauthorized operations or information disclosure. Exploitable via width. Mitigation: upgrade to 1.11.3 or later.

Original description

The description as published by the source.

Impact

A denial-of-service (infinite loop) can occur in text() / textSync() when
both:

  • whitespaceBreak: true is set, and
  • width is set smaller than the rendered width of a single FIGlet character.
    Under these conditions breakWord() could never find a valid break point, so the
    word-wrapping loop in generateFigTextLines() never terminated. This pins a CPU
    core and grows memory without bound, blocking the Node.js event loop.

Severity

Low or Medium. Triggering requires a non-default configuration (whitespaceBreak: true) and
an attacker-controlled width value reaching text()/textSync(). This library is typically
used with fixed options, where this is not
reachable. Applications that pass an untrusted width together with
whitespaceBreak on a request path are affected.

Patches

Fixed in figlet 1.11.3. breakWord() now always makes forward progress
(emitting an over-wide character on its own line), and FIGlet header parsing now
rejects invalid values (e.g. zero/negative height).

Workarounds

Do not expose width to untrusted input, or leave whitespaceBreak disabled
(the default), or upgrade to 1.11.3.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-96780 has been found in figlet.
Attackers can target a specific entry point like width over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade figlet to 1.11.3 or later.
If unsure, ask your IT team or search "figlet CVE-2026-96780" on the vendor's site.

CVE-2026-96780 (figlet) — CWE-835
Attack surface: width / whitespaceBreak
Patched: 1.11.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-835) exists in figlet. Attackers reach the vulnerable code path via width.

📍 Affected scope

Check the vendor advisory for the affected versions of figlet. Attack surface: width / whitespaceBreak.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.11.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'figlet' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'figlet' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で figlet を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade figlet to 1.11.3

    ステージング環境で 1.11.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm figlet
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.11.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details