CVE-2026-16770: PDF::WebKit versions through 1.2 for Perl allow argument injection into wkhtmltopdf via meta tags in the source document
PDF::WebKit versions through 1.2 for Perl allow argument injection into wkhtmltopdf via meta tags in the source document.
For an HTML string or file source, the constructor collects every <meta name="pdf-webkit-KEY" content="VALUE"> element in the document head through _pdf_webkit_meta_tags and turns each one into a wkhtmltopdf command line option. KEY is normalized to an option name matching --[a-z0-9-]+ but is not checked against an allow list, VALUE is passed through unchanged as the argument that follows it, and a VALUE of "yes" emits the option as a bare flag. BUILD merges the meta derived options last, so they also override the module defaults and the options passed to new. Switches such as --enable-local-file-access and --cookie-jar are reachable this way. The renderer is executed with an argument list rather than a shell command, so this is argument injection and not shell injection.
Any caller that renders untrusted HTML lets the document choose the renderer's options and override those set by the application, including options that read local files into the resulting PDF or write to a chosen path. A URL source is not scanned, and the scan is skipped when XML::LibXML, a recommended dependency, is not installed.
Security readout for executives and security teams
Plain-English summary
Applications using PDF::WebKit to turn untrusted HTML into PDFs may let that HTML alter wkhtmltopdf security settings. An attacker-controlled document could enable local-file access, expose local data through a generated PDF, or direct output to an unintended path. The issue is critical where external users control rendered HTML.
Executive priority
Prioritize immediate assessment for public or partner-facing PDF generation services. Patch or remove untrusted rendering promptly when the exposure conditions are present. Systems rendering only trusted content, URL sources, or operating without the scanner dependency have lower documented exposure, but should still be inventoried and reviewed.
Technical view
PDF::WebKit through 1.2 converts specially named HTML meta tags into unrestricted wkhtmltopdf arguments. Meta-derived options are merged last, allowing application defaults and constructor options to be overridden. Values are passed as arguments, while “yes” creates a bare flag. Execution uses an argument list, making this CWE-88 argument injection rather than shell injection.
Likely exposure
Exposure is most likely where PDF::WebKit through 1.2 renders attacker-controlled HTML strings or files and XML::LibXML is installed. URL sources are not scanned, and meta-tag scanning is skipped without XML::LibXML. The supplied records do not establish how widely these conditions occur.
Exploitation context
The source bundle reports CVSS 9.8 but provides no evidence of active exploitation, and the CVE is not listed as KEV. Exploitation requires control over rendered HTML under the documented conditions. Consequences may include local-file disclosure through generated PDFs or writes to attacker-selected paths, depending on wkhtmltopdf privileges.
Researcher notes
Important boundaries are the source type, XML::LibXML availability, option merge order, and renderer privileges. Meta keys are syntax-normalized but not allow-listed; values remain arguments, and “yes” produces flags. Because no shell command is constructed, classify this as argument injection. The supplied sources do not establish exploitation prevalence or a fixed package release.
Mitigation direction
Apply the published MetaCPAN patch after testing it against application PDF workflows.
Until patched, prevent PDF::WebKit from rendering untrusted HTML strings or files.
Remove or strictly allow-list document-derived wkhtmltopdf options.
Run PDF rendering with minimal filesystem permissions and isolated output directories.
Check the project issue and maintainer guidance for an updated release.
Validation and detection
Inventory installed PDF-WebKit versions and determine whether the published patch is present.
Trace whether external or user-controlled HTML reaches PDF::WebKit string or file constructors.
Confirm whether XML::LibXML is installed in each rendering environment.
Test that document meta tags cannot enable unauthorized options or override application settings.
Review renderer permissions and verify generated PDFs cannot disclose unintended local files.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-88: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-88 · source CWE mapping
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.