
Loading

Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: < 0.19.0
Patched in 0.19.0
Details
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.
The height is taken directly from attacker-controlled HTML/CSS (height, vh
units), so a few bytes such as:
<div style="height:99999999px"></div>
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's remaining -= last_slice_h
decrement never terminate, causing an infinite loop.
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.
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.
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.
fulgur performs no network I/O of its own; it renders HTML/CSS handed to it by
the embedding application. This advisory scores the crate independent of any
specific adopting program, so per the CVSS v3.1 User Guide §3.7 (scoring library
vulnerabilities related to incoming data) the Attack Vector is assessed as
Network for the reasonable worst-case deployment — a network-facing service
that renders untrusted, attacker-supplied HTML without user interaction. A
concrete system that receives the HTML in one component and passes it to fulgur
in a separate component may assess a lower environmental Attack Vector (Local,
per §3.10).
EPSS, exploit probability
Low0.61%
estimated chance of real-world exploitation in the next 30 days, higher than 49.2% of every CVE FIRST.org scores
Refreshed 11/2/2026, via FIRST.org's EPSS model, not CVSS, this measures likelihood of exploitation, not how severe it would be.
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.