{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34071 exists.","fix":"No fix has been published for CVE-2026-34071 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34071 is a medium-severity cross-site scripting vulnerability in Stirling-Tools Stirling-PDF, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-34071 and fix it if it is affected.\n\nWhat it is: CVE-2026-34071 is a medium-severity cross-site scripting vulnerability in Stirling-Tools Stirling-PDF, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34071 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-34071/ (Markdown: https://insights.sbomify.com/CVE-2026-34071/index.md)","id":"CVE-2026-34071","markdown":"https://insights.sbomify.com/CVE-2026-34071/index.md","name":"CVE-2026-34071","record":{"aliases":["GHSA-xmhg-fv84-jgfc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PDF processing web app","requires_auth":"none","summary":"Attackers can execute JavaScript in victim browsers by sending malicious emails that trigger unsanitized HTML export in Stirling-PDF.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"stirling_pdf","vendor":"stirling"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Stirling-PDF is a locally hosted web application that allows you to perform various operations on PDF files. In version 2.7.3, the /api/v1/convert/eml/pdf endpoint with parameter downloadHtml=true returns unsanitized HTML from the email body with Content-Type: text/html. An attacker who sends a malicious email to a Stirling-PDF user can achieve JavaScript execution when that user exports the email using the \"Download HTML intermediate file\" feature. Version 2.8.0 fixes 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 has Stored Cross Site Scripting (XSS) via EML-to-HTML Export","id":"CVE-2026-34071","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"cronmaster: Middleware authentication bypass enabling unauthorized page access and server-action execution","id":"CVE-2026-34072"},"packages":[],"prev":{"headline":"LangChain Core has Path Traversal vulnerabilites in legacy `load_prompt` functions","id":"CVE-2026-34070"},"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.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"}],"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":"Attackers can execute JavaScript in victim browsers by sending malicious emails that trigger unsanitized HTML export in Stirling-PDF.","url":"https://insights.sbomify.com/CVE-2026-34071/"}