<?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://cve.radiocsirt.org</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>Sun, 04 Oct 2026 14:21:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68523 — Fulgur: Unbounded page slicing from attacker-controlled CSS height causes denial of service</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-68523</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; fulgur-rs fulgur&lt;/p&gt;
&lt;p&gt;`fulgur` converts untrusted HTML/CSS into PDF, commonly on a server that processes input supplied by many tenants. In versions prior to 0.19.0, a body-direct child whose CSS-resolved height greatly exceeds the page height was sliced into one fragment per page with no upper bound. This is fixed in 0.19.0. A `MAX_PAGES` cap bounds the slice loop — halting it even
for a `+inf` height — and non-finite layout heights are sanitized so they can no longer drive the loop. As a workaround, validate or constrain untrusted CSS (in particular `height` / `vh` on body-level elements) before passing HTML to fulgur.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; fulgur-rs fulgur&lt;/p&gt;
&lt;p&gt;`fulgur` converts untrusted HTML/CSS into PDF, commonly on a server that processes input supplied by many tenants. In versions prior to 0.19.0, a body-direct child whose CSS-resolved height greatly exceeds the page height was sliced into one fragment per page with no upper bound. This is fixed in 0.19.0. A `MAX_PAGES` cap bounds the slice loop — halting it even
for a `+inf` height — and non-finite layout heights are sanitized so they can no longer drive the loop. As a workaround, validate or constrain untrusted CSS (in particular `height` / `vh` on body-level elements) before passing HTML to fulgur.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-68523</guid>
    </item>
    <item>
      <title>GHSA-j5cx-ph8g-95v3 — Fulgur: Unbounded page slicing from attacker-controlled CSS height causes denial of service</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j5cx-ph8g-95v3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: fulgur&lt;/p&gt;
&lt;p&gt;`fulgur` converts untrusted HTML/CSS into PDF, commonly on a server that
processes input supplied by many tenants. In versions prior to 0.19.0, a
body-direct child whose CSS-resolved height greatly exceeds the page height was
sliced into one fragment per page with **no upper bound**.&lt;/p&gt;
&lt;p&gt;The height is taken directly from attacker-controlled HTML/CSS (`height`, `vh`
units), so a few bytes such as:&lt;/p&gt;
&lt;p&gt;```html
&amp;lt;div style=&amp;#34;height:99999999px&amp;#34;&amp;gt;&amp;lt;/div&amp;gt;
```&lt;/p&gt;
&lt;p&gt;forced on the order of 125,000 page fragments. The pagination code then
allocates `vec![Vec::new(); page_count]` and runs a per-page render loop,
resulting in CPU and memory exhaustion. A non-finite height (one that resolves
to `+inf`) additionally made the slicing loop&amp;#39;s `remaining -= last_slice_h`
decrement never terminate, causing an infinite loop.&lt;/p&gt;
&lt;p&gt;An attacker able to submit HTML/CSS to a fulgur-based conversion service can
trigger this with a trivially small payload, denying service to the host and
any co-tenants.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in **0.19.0**. A `MAX_PAGES` cap bounds the slice loop — halting it even
for a `+inf` height — and non-finite layout heights are sanitized so they can no
longer drive the loop.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Upgrade to 0.19.0 or later. If upgrading is not immediately possible, validate
or constrain untrusted CSS (in particular `height` / `vh` on body-level
elements) before passing HTML to fulgur.&lt;/p&gt;
&lt;p&gt;## Attack Vector rationale&lt;/p&gt;
&lt;p&gt;`fulgur` performs no network I/O of its own; it renders HTML/CSS handed to it by
the embedd…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: fulgur&lt;/p&gt;
&lt;p&gt;`fulgur` converts untrusted HTML/CSS into PDF, commonly on a server that
processes input supplied by many tenants. In versions prior to 0.19.0, a
body-direct child whose CSS-resolved height greatly exceeds the page height was
sliced into one fragment per page with **no upper bound**.&lt;/p&gt;
&lt;p&gt;The height is taken directly from attacker-controlled HTML/CSS (`height`, `vh`
units), so a few bytes such as:&lt;/p&gt;
&lt;p&gt;```html
&amp;lt;div style=&amp;#34;height:99999999px&amp;#34;&amp;gt;&amp;lt;/div&amp;gt;
```&lt;/p&gt;
&lt;p&gt;forced on the order of 125,000 page fragments. The pagination code then
allocates `vec![Vec::new(); page_count]` and runs a per-page render loop,
resulting in CPU and memory exhaustion. A non-finite height (one that resolves
to `+inf`) additionally made the slicing loop&amp;#39;s `remaining -= last_slice_h`
decrement never terminate, causing an infinite loop.&lt;/p&gt;
&lt;p&gt;An attacker able to submit HTML/CSS to a fulgur-based conversion service can
trigger this with a trivially small payload, denying service to the host and
any co-tenants.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in **0.19.0**. A `MAX_PAGES` cap bounds the slice loop — halting it even
for a `+inf` height — and non-finite layout heights are sanitized so they can no
longer drive the loop.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Upgrade to 0.19.0 or later. If upgrading is not immediately possible, validate
or constrain untrusted CSS (in particular `height` / `vh` on body-level
elements) before passing HTML to fulgur.&lt;/p&gt;
&lt;p&gt;## Attack Vector rationale&lt;/p&gt;
&lt;p&gt;`fulgur` performs no network I/O of its own; it renders HTML/CSS handed to it by
the embedd…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j5cx-ph8g-95v3</guid>
    </item>
  </channel>
</rss>
