{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27625 exists.","fix":"No fix has been published for CVE-2026-27625 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27625 is a high-severity path traversal vulnerability in Stirling-Tools Stirling-PDF, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-27625 and fix it if it is affected.\n\nWhat it is: CVE-2026-27625 is a high-severity path traversal vulnerability in Stirling-Tools Stirling-PDF, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27625 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-27625/ (Markdown: https://insights.sbomify.com/CVE-2026-27625/index.md)","id":"CVE-2026-27625","markdown":"https://insights.sbomify.com/CVE-2026-27625/index.md","name":"CVE-2026-27625","record":{"aliases":["GHSA-wccq-mg6x-2w22"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PDF processing web app","requires_auth":"low_privilege","summary":"Authenticated users can exploit path traversal in ZIP extraction to write arbitrary files, potentially compromising data integrity or executing code.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"stirling_pdf","vendor":"stirling"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-23","name":"Relative Path Traversal"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Stirling-PDF Zip Slip: Arbitrary File Write via Path Traversal in Markdown-to-PDF ZIP Extraction","id":"CVE-2026-27625","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"OliveTin: OS Command Injection via `password` argument type and webhook JSON extraction bypasses shell safety checks","id":"CVE-2026-27626"},"packages":[],"prev":{"headline":"Coturn: IPv4-mapped IPv6 (::ffff:0:0/96) bypasses denied-peer-ip ACL","id":"CVE-2026-27624"},"products":["Stirling-PDF"],"published":"2026-03-20","related":[{"cvss_score":6.5,"headline":"Stirling-PDF vulnerable to DoS via add-watermark","id":"CVE-2026-33438","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":6.1,"headline":"Stirling-PDF: Reflected XSS through crafted PDF metadata fields (Title and Author)","id":"CVE-2026-41580","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":5.4,"headline":"Stirling-PDF has Stored Cross Site Scripting (XSS) via EML-to-HTML Export","id":"CVE-2026-34071","kev_date_added":null,"published":"2026-03-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-20","vendors":["Stirling-Tools"]},"summary":"Authenticated users can exploit path traversal in ZIP extraction to write arbitrary files, potentially compromising data integrity or executing code.","url":"https://insights.sbomify.com/CVE-2026-27625/"}