{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41580 exists.","fix":"No fix has been published for CVE-2026-41580 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41580 is a medium-severity cross-site scripting vulnerability in Stirling-Tools Stirling-PDF, published on 15 Jul 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-41580 and fix it if it is affected.\n\nWhat it is: CVE-2026-41580 is a medium-severity cross-site scripting vulnerability in Stirling-Tools Stirling-PDF, published on 15 Jul 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-41580 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-41580/ (Markdown: https://insights.sbomify.com/CVE-2026-41580/index.md)","id":"CVE-2026-41580","markdown":"https://insights.sbomify.com/CVE-2026-41580/index.md","name":"CVE-2026-41580","record":{"aliases":["GHSA-rjjx-43g5-mp76"],"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 arbitrary JavaScript in victim browsers via crafted PDF metadata fields 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":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 facilitates various operations on PDF files. Prior to 2.0.0, Stirling-PDF's /get-info-on-pdf endpoint rendered PDF Title and Author metadata fields without proper HTML encoding or sanitization, allowing a crafted PDF to execute attacker-controlled JavaScript in the browser of a user who views the resulting page. This issue is fixed in version 2.0.0.","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: Reflected XSS through crafted PDF metadata fields (Title and Author)","id":"CVE-2026-41580","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Frappe Vulnerable to Possible SQL Injection via get_blog_list","id":"CVE-2026-41581"},"packages":[],"prev":{"headline":"runc: Malicious image with /dev symlink can trigger limited host filesystem integrity violations","id":"CVE-2026-41579"},"products":["Stirling-PDF"],"published":"2026-07-15","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":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-07-15","vendors":["Stirling-Tools"]},"summary":"Attackers can execute arbitrary JavaScript in victim browsers via crafted PDF metadata fields in Stirling-PDF.","url":"https://insights.sbomify.com/CVE-2026-41580/"}