Is CVE-2026-41580 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41580 being exploited in the wild.

How severe is CVE-2026-41580?

Medium severity, with a CVSS score of 6.1, published 15 July 2026.

Which products and versions are affected?

Stirling-Tools Stirling-PDF < 2.0.0.

Is there a fix for CVE-2026-41580?

A patch was published on 2023-11-25: Version 2.0.0 released (based on GitHub release date) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-41580 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-41580?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41580: Stirling-Tools Stirling-PDF XSS in /get-info-on-pdf endpoint

Q: Is there a fix for CVE-2026-41580?

A patch was published on 2023-11-25: Version 2.0.0 released (based on GitHub release date) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-41580 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-41580?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41580 · Severity: medium · CVSS 6.1 · Published 2026-07-15

Stirling-PDF is a web-based tool used for managing and editing PDF documents. A security flaw allows attackers to hide malicious code inside a PDF's metadata (like the Title or Author fields). If a user uploads or views information about such a file, the malicious code could execute in their browser, potentially allowing the attacker to steal session information or perform actions on the user's behalf.

Quick answers

Is CVE-2026-41580 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41580 being exploited in the wild.
How severe is CVE-2026-41580?: Medium severity, with a CVSS score of 6.1, published 15 July 2026.
Which products and versions are affected?: Stirling-Tools Stirling-PDF < 2.0.0.
Is there a fix for CVE-2026-41580?: A patch was published on 2023-11-25: Version 2.0.0 released (based on GitHub release date) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41580 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-41580?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A reflected cross-site scripting (XSS) vulnerability exists in Stirling-PDF versions prior to 2.0.0. The root cause is the failure of the /get-info-on-pdf endpoint to properly HTML-encode or sanitize the 'Title' and 'Author' metadata fields extracted from uploaded PDF files before rendering them in the browser. An attacker can exploit this by crafting a PDF with malicious JavaScript in these metadata fields. When a user interacts with the application to view the info of the crafted PDF, the script executes in the context of the user's session. This can lead to session hijacking, exfiltration of sensitive data from local storage, or DOM manipulation. The issue is resolved in version 2.0.0.

Affected products

Stirling-Tools Stirling-PDF < 2.0.0

Timeline

2026-05-23: advisory: GitHub Security Advisory published
2026-07-15: disclosed: CVE published to NVD
2023-11-25: patched: Version 2.0.0 released (based on GitHub release date)

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.