{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85714 exists.","fix":"No fix has been published for CVE-2026-85714 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85714 is a critical code injection vulnerability in Stirling-Tools Stirling-PDF, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-85714 and fix it if it is affected.\n\nWhat it is: CVE-2026-85714 is a critical code injection vulnerability in Stirling-Tools Stirling-PDF, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85714 exists.\n\nAffected product: Stirling-Tools Stirling-PDF. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-85714/ (Markdown: https://insights.sbomify.com/CVE-2026-85714/index.md)","id":"CVE-2026-85714","markdown":"https://insights.sbomify.com/CVE-2026-85714/index.md","name":"CVE-2026-85714","record":{"aliases":["GHSA-mrr8-934j-4g8m"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PDF processing web app","requires_auth":"high_privilege","summary":"An authenticated administrator can achieve remote code execution by uploading a crafted SQL file that bypasses validation in the H2 database import feature.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Stirling-PDF is a locally hosted web application that facilitates various operations on PDF files. Prior to 2.13.2, an authenticated administrator using the default H2 database and security mode can upload a crafted SQL file to POST /api/v1/database/import-database. DatabaseService.validateSqlContent() splits normalized input on semicolons and accepts a statement when it contains any allowed keyword, allowing dangerous H2 functions such as FILE_READ and CSVWRITE, plus CREATE ALIAS, to bypass the insufficient whitelist and execute side effects when RUNSCRIPT processes the file. This permits arbitrary file access. The demonstrated operating-system command execution chain writes attacker-controlled startup files to a user-site location and then triggers an application Python interpreter configured to load those startup files, resulting in command execution as the JVM service account. This issue is fixed in version 2.13.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-85714.yaml","stars":null,"title":"Stirling PDF \u003c= 2.13.1 - H2 Database Import Remote Code Execution"}],"tier":"weaponised"},"has_fix":false,"headline":"Stirling-PDF: Remote Code Execution via H2","id":"CVE-2026-85714","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ExifReader: DoS via Crafted HEIC/AVIF iloc Box - Memory Exhaustion","id":"CVE-2026-85715"},"packages":[],"prev":{"headline":"LightRAG: Sensitive Information Exposure Through Raw Exception Messages in API Error Responses","id":"CVE-2026-85709"},"products":["Stirling-PDF"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Stirling-Tools"]},"summary":"An authenticated administrator can achieve remote code execution by uploading a crafted SQL file that bypasses validation in the H2 database import feature.","url":"https://insights.sbomify.com/CVE-2026-85714/"}