Quick answers
- Is CVE-2026-85714 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85714 being exploited in the wild.
- How severe is CVE-2026-85714?
- Critical severity, with a CVSS score of 9.1, published 14 October 2026.
- Which products and versions are affected?
- Stirling-Tools Stirling-PDF prior to 2.13.2.
- Is there a fix for CVE-2026-85714?
- Yes: fixed in 2.13.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-85714 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-85714?
- Check whether you run Stirling-Tools Stirling-PDF at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.13.2
Technical details
The vulnerability is a SQL injection in DatabaseService.validateSqlContent() where the whitelist validation splits input on semicolons and accepts statements containing allowed keywords, permitting bypass via H2 database functions like FILE_READ, CSVWRITE, and CREATE ALIAS. An authenticated administrator can POST a crafted SQL file to /api/v1/database/import-database; RUNSCRIPT processing executes the injected functions to read files or create aliases that load attacker-controlled startup scripts, achieving remote code execution as the JVM service account.
Affected products
- Stirling-Tools Stirling-PDF prior to 2.13.2
Timeline
- 2026-10-14: disclosed
- 2026-06-24: patched