dbcve.org
Stirling PdfApplication · Stirlingpdf

CVE-2025-55150

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-11
Fix available
A fix is available. Upgrade to 1.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 performs various operations on PDF files. Prior to version 1.1.0, when using the /api/v1/convert/html/pdf endpoint to convert HTML to PDF, the backend calls a third-party tool to process it and includes a sanitizer for security sanitization which can be bypassed and result in SSRF. This issue has been patched in version 1.1.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 prior to version 1.1.0 contains an SSRF vulnerability in the /api/v1/convert/html/pdf endpoint. The backend calls a third-party tool to process HTML-to-PDF conversions, and a security sanitizer intended to prevent malicious requests can be bypassed, allowing attackers to make the server perform arbitrary requests to internal or external resources.

MitigationUpgrade to Stirling-PDF version 1.1.0 or later to patch the sanitizer bypass. As a locally hosted application, network segmentation and restricting outbound access from the server provide additional defense-in-depth layers.

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:< 1.1.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installed Stirling-PDF version
    Locate the Stirling-PDF application and check its version number (typically visible in the web UI footer, in startup logs, or via API endpoint like /api/v1/info/version). Compare it to the affected range: versions prior to 1.1.0 are vulnerable.
    Affected if The installed version is less than 1.1.0.
  2. Confirm the vulnerable endpoint is exposed
    Verify that the web interface or API is accessible and that the /api/v1/convert/html/pdf endpoint is available. This endpoint handles HTML-to-PDF conversion requests.
    Affected if The endpoint /api/v1/convert/html/pdf is accessible and functional.
  3. Check for outbound network access
    Inspect the Stirling-PDF server network configuration and firewall rules to determine whether the application process can initiate outbound HTTP/HTTPS requests to arbitrary addresses.
    Affected if The Stirling-PDF server has unrestricted outbound network access.
  4. Review access logs for suspicious requests
    Examine application access logs and web server logs for requests to /api/v1/convert/html/pdf that contain unusual URLs, internal IP addresses (such as 127.0.0.1, 192.168.x.x, 10.x.x.x), or cloud metadata endpoints (such as 169.254.169.254).
    Affected if Logs contain evidence of SSRF attempts or unexpected internal resource access via the HTML-to-PDF endpoint.

You are affected if Stirling-PDF version is below 1.1.0 AND the /api/v1/convert/html/pdf endpoint is accessible and enabled.

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 1.1.0 or later
Fixed in 1.1.0
Vendor patch github.com →
Interim mitigation

Upgrade to Stirling-PDF version 1.1.0 or later to patch the sanitizer bypass. As a locally hosted application, network segmentation and restricting outbound access from the server provide additional defense-in-depth layers.

Recommended fix High confidence

1.1.0

  1. Verify current version by checking the running container or application version
  2. Backup any existing data, configurations, and PDF files stored in the application
  3. If using Docker, pull the latest image tag 1.1.0 or the specific version tag: docker pull stirlingtools/stirling-pdf:1.1.0
  4. Redeploy the container with the new image version
  5. If using manual installation, download Stirling-PDF version 1.1.0 from the official releases and replace the existing installation
  6. Restart the application service
  7. Verify the upgrade was successful by checking the application version and testing the /api/v1/convert/html/pdf endpoint

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55150 — 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-2025-55150 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