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

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-30).

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

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality low, integrity none, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 4 references on Exploit Observer

Live scores

EPSS
0.004
low predicted chance of attack
VEDAS
0.972
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Suricata

Who is affected

ProductAffectedNot affected
Stirling-Tools Stirling-PDFversion >= 2.13.1, < 2.13.2Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-119342 Stirling-PDF - Local File Disclosure via SVG-to-PDF Convert Attempt. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-119342 Stirling-PDF - Local File Disclosure via SVG-to-PDF Convert Attempt"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/v1/convert/svg/pdf"; nocase; fast_pattern; http.request_body; content:"fileInput"; nocase; content:"<image"; nocase; pcre:"/(xlink\x3ahref|href)\s*=\s*[\x22\x27]?(\.\.\/|\/)/i"; classtype:web-application-attack; reference:cve,CVE-2026-119342; reference:url,https://www.exploit.observer/?keyword=CVE-2026-119342&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=stirlingpdf&match=exact; sid:1105001; rev:1;)

CVE-2026-119342.rules on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust