# CVE-2026-113605: Stirling-PDF 2.13.2 through 3.2.0 H2 SQL Denylist Bypass via import-database


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-j8f5-2f4f-jm2m

## What is CVE-2026-113605?

CVE-2026-113605 is a high-severity vulnerability in Stirling-Tools Stirling-PDF, published on 20 Oct 2026. 

### Official description

Stirling-PDF from 2.13.2 through 3.2.0 contains an incomplete denylist in DatabaseService.validateSqlContent() that allows administrators to bypass H2 import restrictions using CREATE OR REPLACE ALIAS. Authenticated administrators can upload a crafted SQL backup to the import-database endpoint, where RUNSCRIPT defines H2 Java function aliases and restores Java-method execution.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

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


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

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

## Is CVE-2026-113605 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113605 is a high-severity vulnerability in Stirling-Tools Stirling-PDF, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113605 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-113605/ (Markdown: https://insights.sbomify.com/CVE-2026-113605/index.md)
```

## Sources

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

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