CVE-2026-27625: Stirling-PDF · Path Traversal
Affects Stirling-PDFSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 2.5.2 soon.
Data as of 31 Oct 2026, 20:20 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.
What to do
Upgrade Stirling-PDF and stirling-tools/Stirling-PDF to 2.5.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Stirling-ToolsStirling-PDF | Affected
| Fixed in
|
GitHubstirling-tools/Stirling-PDFpkg:github/stirling-tools/Stirling-PDFOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Upgrade Stirling-PDF to version 2.5.2 or later, where the vulnerability is fixed with proper path validation during ZIP extraction.
- Restrict access to the Stirling-PDF application to trusted users only and enforce strong authentication mechanisms to reduce the risk of unauthorized exploitation.
- Implement strict file system permissions for the stirlingpdfuser process, limiting write access only to necessary directories to minimize the impact of arbitrary file writes.
- Monitor application logs and file system changes for unusual activity indicative of exploitation attempts, such as unexpected file modifications outside the temporary directory.
- Employ network segmentation and application-level firewalls to limit exposure of the Stirling-PDF service to internal or trusted networks.
- Conduct regular security audits and penetration tests focusing on file upload and extraction functionalities to detect similar path traversal issues.
- Educate users about the risks of sharing credentials and enforce least privilege principles to reduce the attack surface.
Description
Stirling-PDF is a locally hosted web application that performs various operations on PDF files. In versions prior to 2.5.2, the /api/v1/convert/markdown/pdf endpoint extracts user-supplied ZIP entries without path checks. Any authenticated user can write files outside the intended temporary working directory, leading to arbitrary file write with the privileges of the Stirling-PDF process user (stirlingpdfuser). This can overwrite writable files and compromise data integrity, with further impact depending on writable paths. The issue was fixed in version 2.5.2.