Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-71270 – Server-Side Request Forgery (SSRF) – Stirling-PDF (all versions)

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-71270 is a Server-Side Request Forgery (SSRF) vulnerability (CWE-918) in Stirling-PDF, a self-hosted web application for performing operations on PDF files. The flaw resides in the POST /api/v1/convert/url/pdf endpoint, which lacks the SSRF protections present in sibling conversion endpoints, allowing an unauthenticated attacker to retrieve cloud metadata and internal network resources. It carries a CVSS v3.1 base score of 8.6 (High).

Technical details

  • Root cause: The /api/v1/convert/url/pdf endpoint (implemented in ConvertWebsiteToPDF.java) validates only the initial URL resolution to public IPs but does not sanitize embedded resource references in the fetched HTML. The WeasyPrint subprocess that renders the page then processes those references without per-resource SSRF filtering.
  • Trigger conditions: An attacker supplies a target webpage containing malicious embedded resource references, which the server fetches and processes when generating the PDF.
  • Attack vector: Network (AV:N); no authentication (PR:N) and no user interaction (UI:N) required.
  • Impact: High confidentiality impact. Data from cloud metadata endpoints (e.g., 169.254.169.254) or internal networks can be leaked into the generated PDF. The CVSS vector indicates a scope change (S:C) with no integrity or availability impact.

Affected software

  • Stirling-PDF: all versions (marked affected from version 0 onward per the CVE record).

Severity

  • CVSS v3.1 Base Score: 8.6 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: No patched version is listed in the CVE record at time of writing. Monitor the Stirling-Tools GitHub repository and security advisories for an official fix and upgrade as soon as one is published.
  • If no patch: Restrict the Stirling-PDF host’s egress so it cannot reach internal subnets, link-local addresses, or cloud metadata services (e.g., 169.254.169.254) at the network or container layer. Run Stirling-PDF in an isolated network segment with no route to sensitive internal services, and disable or block the URL-to-PDF conversion endpoint if it is not required.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Stirling-PDF
  • Raw response body: window.stirlingPDF = window.stirlingPDF || {}, stirlingPDFLabel = "Stirling-PDF"

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge