{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33438 exists.","fix":"No fix has been published for CVE-2026-33438 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33438 is a medium-severity denial of service vulnerability in Stirling-Tools Stirling-PDF, published on 26 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-33438 and fix it if it is affected.\n\nWhat it is: CVE-2026-33438 is a medium-severity denial of service vulnerability in Stirling-Tools Stirling-PDF, published on 26 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-33438 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-33438/ (Markdown: https://insights.sbomify.com/CVE-2026-33438/index.md)","id":"CVE-2026-33438","markdown":"https://insights.sbomify.com/CVE-2026-33438/index.md","name":"CVE-2026-33438","record":{"aliases":["GHSA-3932-2rfq-87xm"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"PDF processing web app","requires_auth":"low_privilege","summary":"Authenticated attackers can crash Stirling-PDF servers by submitting extreme parameter values to the add-watermark endpoint.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"stirling_pdf","vendor":"stirling"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Stirling-PDF is a locally hosted web application that allows you to perform various operations on PDF files. Versions starting in 2.1.5 and prior to 2.5.2 have Denial of Service (DoS) vulnerability in the Stirling-PDF watermark functionality (`/api/v1/security/add-watermark` endpoint). The vulnerability allows authenticated users to cause resource exhaustion and server crashes by providing extreme values for the `fontSize` and `widthSpacer` parameters. Version 2.5.2 patches the issue.","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 vulnerable to DoS via add-watermark","id":"CVE-2026-33438","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Pre-Authentication Remote Code Execution via `jato.clientSession` Deserialization in OpenAM","id":"CVE-2026-33439"},"packages":[],"prev":{"headline":"Stirling PDF: Stored XSS in Info Summary","id":"CVE-2026-33437"},"products":["Stirling-PDF"],"published":"2026-03-26","related":[{"cvss_score":8.1,"headline":"Stirling-PDF Zip Slip: Arbitrary File Write via Path Traversal in Markdown-to-PDF ZIP Extraction","id":"CVE-2026-27625","kev_date_added":null,"published":"2026-03-20"},{"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-26","vendors":["Stirling-Tools"]},"summary":"Authenticated attackers can crash Stirling-PDF servers by submitting extreme parameter values to the add-watermark endpoint.","url":"https://insights.sbomify.com/CVE-2026-33438/"}