dbcve.org
Stirling PdfApplication · Stirling

CVE-2026-41580

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stirling-PDF versions prior to 2.0.0 contain a stored cross-site scripting (XSS) vulnerability in the /get-info-on-pdf endpoint. The PDF Title and Author metadata fields are rendered without HTML encoding, allowing malicious metadata to execute arbitrary JavaScript in the browser of users viewing the PDF information page.

MitigationUpgrade Stirling-PDF to version 2.0.0 or later. As a defense-in-depth measure, ensure users do not view untrusted PDFs directly in the application without confirming the source.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Stirling PdfApplication
Affected:< 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Stirling-PDF installation
    Locate the Stirling-PDF application in your environment. This is typically a web application running on a Java servlet container or as a Docker container. Check your running services or deployed applications for anything named 'Stirling-PDF' or 'stirling-pdf'.
    Affected if Stirling-PDF is not present in your environment, you are not affected.
  2. Determine installed version
    Check the version of your Stirling-PDF installation. This is usually visible in the web UI footer, in the Docker image tag, or in the application's startup logs. Compare your version against 2.0.0.
    Affected if Your installed version is prior to 2.0.0, the application contains the vulnerability.
  3. Verify /get-info-on-pdf endpoint is accessible
    Confirm that the /get-info-on-pdf endpoint is available and functional in your deployment. This endpoint provides PDF metadata information including Title and Author fields. Attempt to access it or check your application's routing configuration.
    Affected if The endpoint is disabled or not exposed, the attack surface may be reduced but the vulnerable code likely still exists in the application.
  4. Audit uploaded PDFs for metadata
    Review any PDFs stored in your Stirling-PDF instance for suspicious metadata. Examine PDF files that may have been uploaded by untrusted users, looking for unusual content in the Title or Author metadata fields that could contain script tags or HTML.
    Affected if You have PDFs with unsanitized Title or Author metadata from untrusted sources, and users view them via the info endpoint, the XSS can be triggered.

You are affected if Stirling-PDF version prior to 2.0.0 is installed and users can upload or view PDFs with arbitrary metadata through the /get-info-on-pdf endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.0 or later
Fixed in 2.0.0
Interim mitigation

Upgrade Stirling-PDF to version 2.0.0 or later. As a defense-in-depth measure, ensure users do not view untrusted PDFs directly in the application without confirming the source.

Recommended fix High confidence

2.0.0

  1. Identify the current Stirling-PDF version running in your environment
  2. Stop the Stirling-PDF service
  3. Back up the existing installation and any PDF files or configurations
  4. Upgrade Stirling-PDF to version 2.0.0 using your installation method (e.g., Docker pull, package manager, or direct download)
  5. Restart the Stirling-PDF service
  6. Verify the application is running version 2.0.0
  7. Test the /get-info-on-pdf endpoint to confirm the vulnerability is remediated
Caveat Review the 2.0.0 release notes for any breaking changes or configuration changes compared to your current version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Stirling Pdf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41580 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41580 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data