CVE-2026-68523: Fulgur Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-j5cx-ph8g-95v3
CVSS 7.5
CWE-400 CWE-835
Published
Advisory Summary

CVE-2026-68523 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Fulgur libraries in the crates.io ecosystem. The issue involves unbounded page slicing from attacker-controlled css height causes denial of service. Remediation is available by upgrading affected packages to version 0.19.0.

CVE-2026-68523 at a Glance

CVE Identifier CVE-2026-68523
GHSA Identifier GHSA-j5cx-ph8g-95v3
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product Fulgur
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-68523

To remediate this vulnerability, upgrade all affected Fulgur dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

fulgur fixed: 0.19.0
Upgrade fulgur to 0.19.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for fulgur

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-68523, inspect your project dependencies for Fulgur:

inspect dependencies for fulgur

Analyze the terminal output to locate any version of Fulgur in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.19.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Fulgur, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

`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: ```html <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. ## Patches 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. ## Workarounds 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. ## 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 (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). ## References - Fix: https://github.com/fulgur-rs/fulgur/pull/501

CVE-2026-68523 Affected Fulgur Versions

1 component(s)
Fixed Versions:
0.19.0
Product / Package Ecosystem Affected Versions Fixed Version
fulgur
crates.io
< 0.19.0
0.19.0

References

Frequently Asked Questions

What is CVE-2026-68523?
CVE-2026-68523 is a security vulnerability in Fulgur involving Unbounded page slicing from attacker-controlled CSS height causes denial of service under CWE-400: Uncontrolled Resource Consumption.
Which Fulgur versions are affected?
Affected versions include releases prior to 0.19.0 across affected packages: fulgur.
What version fixes CVE-2026-68523?
Upgrading to 0.19.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is fulgur affected?
Yes, fulgur is affected in releases prior to 0.19.0. Upgrade your dependency to 0.19.0 or later.
What is the CVSS score of CVE-2026-68523?
CVE-2026-68523 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-68523?
CVE-2026-68523 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check crates.io dependencies for CVE-2026-68523?
Run the dependency tree command: 'inspect dependencies for fulgur'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-j5cx-ph8g-95v3",
  "modified" : "2026-09-17T18:48:55Z",
  "published" : "2026-09-17T18:48:55Z",
  "aliases" : [ "CVE-2026-68523" ],
  "summary" : "Fulgur: Unbounded page slicing from attacker-controlled CSS height causes denial of service",
  "details" : "`fulgur` converts untrusted HTML/CSS into PDF, commonly on a server that\nprocesses input supplied by many tenants. In versions prior to 0.19.0, a\nbody-direct child whose CSS-resolved height greatly exceeds the page height was\nsliced into one fragment per page with **no upper bound**.\n\nThe height is taken directly from attacker-controlled HTML/CSS (`height`, `vh`\nunits), so a few bytes such as:\n\n```html\n<div style=\"height:99999999px\"></div>\n```\n\nforced on the order of 125,000 page fragments. The pagination code then\nallocates `vec![Vec::new(); page_count]` and runs a per-page render loop,\nresulting in CPU and memory exhaustion. A non-finite height (one that resolves\nto `+inf`) additionally made the slicing loop's `remaining -= last_slice_h`\ndecrement never terminate, causing an infinite loop.\n\nAn attacker able to submit HTML/CSS to a fulgur-based conversion service can\ntrigger this with a trivially small payload, denying service to the host and\nany co-tenants.\n\n## Patches\n\nFixed in **0.19.0**. A `MAX_PAGES` cap bounds the slice loop — halting it even\nfor a `+inf` height — and non-finite layout heights are sanitized so they can no\nlonger drive the loop.\n\n## Workarounds\n\nUpgrade to 0.19.0 or later. If upgrading is not immediately possible, validate\nor constrain untrusted CSS (in particular `height` / `vh` on body-level\nelements) before passing HTML to fulgur.\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 §3.7 (scoring library\nvulnerabilities related to incoming data) the Attack Vector is assessed as\n**Network** for the reasonable worst-case deployment — a network-facing service\nthat renders untrusted, attacker-supplied 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 §3.10).\n\n## References\n\n- Fix: https://github.com/fulgur-rs/fulgur/pull/501",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "fulgur"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.19.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/fulgur-rs/fulgur/security/advisories/GHSA-j5cx-ph8g-95v3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/fulgur-rs/fulgur/pull/501"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/fulgur-rs/fulgur"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2026-0200.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400", "CWE-835" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-17T18:48:55Z",
    "nvd_published_at" : null
  }
}