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


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-pr4g-9qp2-g8j8

## What is CVE-2026-119342?

CVE-2026-119342 is a medium-severity vulnerability in Stirling-Tools Stirling-PDF, published on 30 Oct 2026. 

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-610 (Externally Controlled Reference to a Resource in Another Sphere), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-119342?


## How do I fix CVE-2026-119342?

No fix has been published for CVE-2026-119342 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119342 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119342 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119342 and fix it if it is affected.

What it is: CVE-2026-119342 is a medium-severity vulnerability in Stirling-Tools Stirling-PDF, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119342 exists.

Affected product: Stirling-Tools Stirling-PDF. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119342/ (Markdown: https://insights.sbomify.com/CVE-2026-119342/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119342
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119342
- OSV: https://osv.dev/vulnerability/CVE-2026-119342

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119342/
Summaries are generated and may contain mistakes; the official description above is the record.