CVE-2026-68537 fulgur-rs CVE debrief

Who should care

Defenders responsible for systems using the `fulgur` crate, especially in multi-tenant environments, should assess exposure and prioritize patching or mitigation. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Operators, platforms, and security teams should also be aware of the potential impact and take necessary measures to protect their systems.

Why it matters

Defenders should care about this vulnerability because it allows an attacker to cause significant CPU and memory exhaustion with a small payload, potentially denying service to the host and co-tenants. The vulnerability is especially concerning in multi-tenant environments where an attacker could submit malicious HTML.

• CPU exhaustion due to amplification of blank PDF pages
• Memory exhaustion due to allocation of thousands of pages
• Denial of service to the host and co-tenants
• Potential for trivially small payloads to cause significant impact

Technical summary

The `fulgur` crate, used for converting untrusted HTML/CSS into PDF, is vulnerable to a denial-of-service attack. An attacker can submit a small payload that amplifies into thousands of blank PDF pages, causing CPU and memory exhaustion. The vulnerability is fixed in version 0.26.0 and occurs when a childless box resolves to a pathologically tall height, amplifying into thousands of blank PDF pages. The fix removes a tag-only gate that allowed non-painting replaced elements to bypass the childless-collapse defense.

Defensive priority

Defenders should prioritize patching or mitigating this vulnerability, especially in multi-tenant environments where an attacker could submit malicious HTML.

Recommended defensive actions

• Patch `fulgur` to version 0.26.0 or later
• Restrict HTML submission to trusted sources
• Monitor for unusual PDF generation activity
• Implement additional security measures for multi-tenant environments
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability is caused by a childless box that resolves to a pathologically tall height being amplified into thousands of blank PDF pages. The fix in version 0.26.0 removes a tag-only gate that allowed non-painting replaced elements to bypass the childless-collapse defense.

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.