CVE-2026-68523 fulgur-rs CVE debrief

Who should care

Defenders managing multi-tenant environments where `fulgur` is used to process untrusted HTML/CSS inputs should assess exposure and prioritize upgrading to version 0.19.0 or applying workarounds to constrain untrusted CSS inputs.

Why it matters

CVE-2026-68523 is a denial of service vulnerability in the `fulgur` library that can be exploited by processing untrusted HTML/CSS inputs with excessively large CSS-resolved heights. Defenders should prioritize upgrading to version 0.19.0 or applying workarounds, especially in multi-tenant environments.

• Denial of service through excessive resource consumption
• Potential for service disruption in multi-tenant environments
• Need for validation or constraints on untrusted CSS inputs

Technical summary

The `fulgur` library, used to convert untrusted HTML/CSS into PDF, has a vulnerability that can lead to denial of service. In versions prior to 0.19.0, a body-direct child with a CSS-resolved height greatly exceeding the page height could be sliced into one fragment per page without an upper bound. This issue is addressed in version 0.19.0 by introducing a `MAX_PAGES` cap that bounds the slice loop and sanitizing non-finite layout heights.

Defensive priority

Defenders should prioritize upgrading to version 0.19.0 or applying workarounds to constrain untrusted CSS inputs, particularly for multi-tenant environments.

Recommended defensive actions

• Upgrade to `fulgur` version 0.19.0 or later
• Validate or constrain untrusted CSS inputs, especially `height` and `vh` properties on body-level elements
• Review and adjust multi-tenant environment configurations
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and the fixed version. Vendor and community sources confirm the issue and the workaround. Defenders should verify affected deployments, review official advisories, and plan updates or mitigations. Compensating controls and monitoring can help while remediation is scheduled. Evidence limits and affected scope are noted. CVE Program and NVD records are official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.