rustsec-2026-0201
Vulnerability from osv_rustsec
fulgur converts untrusted HTML/CSS into PDF, commonly on a server that
processes input supplied by many tenants. In versions prior to 0.26.0, a
childless box that resolves to a pathologically tall height was amplified into
thousands of blank PDF pages, even when it produces no visible output.
The childless-collapse defense that would normally collapse such a box was gated
by a tag-only "replaced content" check, so any non-painting replaced element
bypassed it, including an unresolved src (the common offline-first case), a
visibility:hidden image, an undecodable image format, and an empty <svg>. A
trailing-sibling variant of the same gap was also open.
A few bytes of HTML therefore amplified into roughly MAX_PAGES (10,000) blank
pages; the renderer allocates and runs a per-page loop over them, producing CPU
and memory exhaustion. An attacker able to submit HTML 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.26.0: the tag-only gate was removed so that any pathologically tall
childless box collapses regardless of whether it is a replaced element, closing
the missing-src, visibility:hidden, undecodable-format, and empty-<svg>
vectors along with the trailing-sibling variant.
Versions prior to 0.19.0 additionally lacked any page-count cap, allowing an unbounded (rather than 10,000-page) variant of this amplification; that earlier variant is tracked separately as GHSA-j5cx-ph8g-95v3.
Attack Vector rationale
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 the Attack
Vector is assessed as Network for the reasonable worst-case deployment — a
network-facing service that renders untrusted 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).
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"categories": [
"denial-of-service"
],
"cvss": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "fulgur",
"purl": "pkg:cargo/fulgur"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "0.26.0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"GHSA-4rf6-qx84-q9fv"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "`fulgur` converts untrusted HTML/CSS into PDF, commonly on a server that\nprocesses input supplied by many tenants. In versions prior to 0.26.0, a\nchildless box that resolves to a pathologically tall height was amplified into\nthousands of blank PDF pages, even when it produces no visible output.\n\nThe childless-collapse defense that would normally collapse such a box was gated\nby a tag-only \"replaced content\" check, so any non-painting replaced element\nbypassed it, including an unresolved `src` (the common offline-first case), a\n`visibility:hidden` image, an undecodable image format, and an empty `\u003csvg\u003e`. A\ntrailing-sibling variant of the same gap was also open.\n\nA few bytes of HTML therefore amplified into roughly `MAX_PAGES` (10,000) blank\npages; the renderer allocates and runs a per-page loop over them, producing CPU\nand memory exhaustion. An attacker able to submit HTML to a fulgur-based\nconversion service can trigger this with a trivially small payload, denying\nservice to the host and any co-tenants.\n\nFixed in 0.26.0: the tag-only gate was removed so that any pathologically tall\nchildless box collapses regardless of whether it is a replaced element, closing\nthe missing-`src`, `visibility:hidden`, undecodable-format, and empty-`\u003csvg\u003e`\nvectors along with the trailing-sibling variant.\n\nVersions prior to 0.19.0 additionally lacked any page-count cap, allowing an\nunbounded (rather than 10,000-page) variant of this amplification; that earlier\nvariant is tracked separately as GHSA-j5cx-ph8g-95v3.\n\n## Attack Vector rationale\n\n`fulgur` performs no network I/O of its own; it renders HTML/CSS handed to it by\nthe embedding application. This advisory scores the crate independent of any\nspecific adopting program, so per the CVSS v3.1 User Guide \u00a73.7 the Attack\nVector is assessed as Network for the reasonable worst-case deployment \u2014 a\nnetwork-facing service that renders untrusted HTML without user interaction. A\nconcrete system that receives the HTML in one component and passes it to fulgur\nin a separate component may assess a lower environmental Attack Vector (Local,\nper \u00a73.10).",
"id": "RUSTSEC-2026-0201",
"modified": "2026-07-04T20:19:28Z",
"published": "2026-07-05T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/fulgur"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0201.html"
},
{
"type": "ADVISORY",
"url": "https://github.com/fulgur-rs/fulgur/security/advisories/GHSA-4rf6-qx84-q9fv"
}
],
"related": [],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "Non-painting replaced elements amplify to thousands of blank PDF pages (denial of service)"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.