CVE-2026-16770
Argument-injection via HTML meta tags lets untrusted docs control wkhtmltopdf options.
Is CVE-2026-16770 being exploited?
Not confirmed. CVE-2026-16770 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.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-16770?
CVE-2026-16770 is rated Critical with a CVSS score of 9.8. 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-16770?
Yes. A fix has been recorded for CVE-2026-16770. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-16770 affect?
CVE-2026-16770 affects PDF::WebKit (Perl) <=1.2, wkhtmltopdf, Web apps rendering untrusted HTML to PDF. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-16770?
Stop rendering untrusted HTML; sanitize/whitelist meta options; restrict wkhtmltopdf local-file access; upgrade when patch released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-supplied HTML can inject wkhtmltopdf options to read local files, write chosen paths, or alter renderer behavior, enabling data disclosure or file write abuse.
Immediate action required
- affected<= 1.2
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.