{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113606 exists.","fix":"No fix has been published for CVE-2026-113606 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-113606 is a high-severity vulnerability in Stirling-Tools Stirling-PDF, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-113606 and fix it if it is affected.\n\nWhat it is: CVE-2026-113606 is a high-severity vulnerability in Stirling-Tools Stirling-PDF, published on 20 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113606 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-113606/ (Markdown: https://insights.sbomify.com/CVE-2026-113606/index.md)","id":"CVE-2026-113606","markdown":"https://insights.sbomify.com/CVE-2026-113606/index.md","name":"CVE-2026-113606","record":{"aliases":["GHSA-c89m-ff4c-f99w"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Stirling-PDF 3.0.0 through 3.2.0 contains an authorization bypass vulnerability that allows authenticated users to access other users' stored files by pointing a processing folder at the server storage directory. Attackers can create a folder via POST /api/v1/processing-folders targeting storage/\u003cvictimUserId\u003e, list files, and run pipelines to read, modify, or destroy victims' files.","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 3.0.0 through 3.2.0 Authorization Bypass via Processing Folders","id":"CVE-2026-113606","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Configurable Reports block for Moodle before 5.3.0 Authorization Bypass via get_report_data","id":"CVE-2026-113607"},"packages":[],"prev":{"headline":"Stirling-PDF 2.13.2 through 3.2.0 H2 SQL Denylist Bypass via import-database","id":"CVE-2026-113605"},"products":["Stirling-PDF"],"published":"2026-10-20","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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-23","vendors":["Stirling-Tools"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-113606/"}