<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 09:49:08 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-96780</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-96780</link>
      <description>&lt;p&gt;figlet.js is a FIG driver written in JavaScript that aims to implement the FIGfont specification. Prior to 1.11.3, text() and textSync() can enter an unbounded loop when whitespaceBreak is enabled and width is smaller than the rendered width of a single FIGlet character. Under these conditions, breakWord() cannot find a valid break point and returns without consuming a character, so generateFigTextLines() repeatedly processes the same input while consuming CPU and growing memory. The non-default option and attacker-controlled width must both reach an affected call. This issue is fixed in version 1.11.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;figlet.js is a FIG driver written in JavaScript that aims to implement the FIGfont specification. Prior to 1.11.3, text() and textSync() can enter an unbounded loop when whitespaceBreak is enabled and width is smaller than the rendered width of a single FIGlet character. Under these conditions, breakWord() cannot find a valid break point and returns without consuming a character, so generateFigTextLines() repeatedly processes the same input while consuming CPU and growing memory. The non-default option and attacker-controlled width must both reach an affected call. This issue is fixed in version 1.11.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-96780</guid>
    </item>
    <item>
      <title>GHSA-62ch-8vmq-8xm7 — figlet is vulnerable to denial of service via unbounded loop when whitespaceBreak is used with a small width</title>
      <link>https://db.gcve.eu/vuln/ghsa-62ch-8vmq-8xm7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: figlet&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### 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).&lt;/p&gt;
&lt;p&gt;### Workarounds
Do not expose `width` to untrusted input, or leave `whitespaceBreak` disabled
(the default), or upgrade to 1.11.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: figlet&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### 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).&lt;/p&gt;
&lt;p&gt;### Workarounds
Do not expose `width` to untrusted input, or leave `whitespaceBreak` disabled
(the default), or upgrade to 1.11.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-62ch-8vmq-8xm7</guid>
    </item>
  </channel>
</rss>
