Live › vulnerability › CVE-2026-119343
Stirling-PDF's AI agent endpoint for creating PDFs from HTML passes user HTML to WeasyPrint without the sanitizer used elsewhere. An attacker can make the server fetch internal or cloud-metadata URLs and embed local files readable by the Stirling-PDF process into the generated PDF.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 21:25 UTC. All times on this page are UTC.
Instances of Stirling-PDF before 3.0.0 that are reachable by others. The endpoint needs no credentials when login is disabled, so instances with security.enableLogin set to false are most exposed. Instances with login enabled require valid credentials first, and instances not reachable beyond a trusted network carry less risk.
No product ranges from the sources yet.
unknown if the deployment does not report itsecurity.enableLogin is set to false in the configuration/api/v1/ai/tools/create-pdf-from-html-agent3.0.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Stirling-PDF is a locally hosted web application that facilitates various operations on PDF files. Prior to 3.0.0, POST /api/v1/ai/tools/create-pdf-from-html-agent accepts attacker-controlled htmlContent and passes it to WeasyPrint without CustomHtmlSanitizer, unlike the sanitized /api/v1/convert/html/pdf control path. HTTP and HTTPS resource references can make server-side requests to internal or cloud-metadata destinations, while file references can embed local content readable by the Stirling-PDF process into the generated PDF. The endpoint is reachable without credentials when security.enableLogin is false, and the flaw is distinct from earlier Stirling-PDF WeasyPrint vulnerabilities in older conversion paths. This issue is fixed in version 3.0.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-119343")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.