Skip to content
Web

CVE-2026-33437

HIGH
High
EPSS 0.28%Patch availableAug 18, 2026

Stored XSS in Stirling-PDF Get Info allows execution of attacker JS from PDF metadata.

common questions

Is CVE-2026-33437 being exploited?

Not confirmed. CVE-2026-33437 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.

How severe is CVE-2026-33437?

CVE-2026-33437 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-33437?

Yes. A fix has been recorded for CVE-2026-33437. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-33437 affect?

CVE-2026-33437 affects Stirling-PDF <2.0.0, Self-hosted Stirling-PDF web instances, Get Info workflow (get-info-on-pdf.html). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-33437?

Upgrade to Stirling-PDF v2.0.0; block or sanitize untrusted PDF metadata and restrict uploads.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Stirling-PDF <2.0.0Self-hosted Stirling-PDF web instancesGet Info workflow (get-info-on-pdf.html)
impact

Stored XSS via PDF Title/Author metadata; attacker-controlled JS can steal session data, perform actions as user, or modify page content when Get Info is clicked.

action required

Immediate action required

affected versions
Stirling-Tools Stirling-PDF
  • affected< 2.0.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free