# CVE-2026-16766: Catalyst::View::Wkhtmltopdf versions before 0.6.1 for Perl allow shell command injection (RCE) via PDF render options


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Jul 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-42w4-jj8w-6p98

## What is CVE-2026-16766?

CVE-2026-16766 is a critical vulnerability in RRWO Catalyst::View::Wkhtmltopdf, published on 25 Jul 2026. 

### Official description

Catalyst::View::Wkhtmltopdf versions before 0.6.1 for Perl allow shell command injection (RCE) via PDF render options.

Options are passed directly to the wkhtmltopdf command without sanitization.

Any web application that passes user-controlled options such as the page_size, orientation or margins without validation allows shell command injection.

Version 0.6.0 was released with an incomplete fix for this issue.

Note that the wkhtmltopdf project is no longer being developed, and users of this package should migrate to alternative solutions.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-16766?


## How do I fix CVE-2026-16766?

No fix has been published for CVE-2026-16766 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16766 being exploited?

There is no known exploitation of CVE-2026-16766 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16766 and fix it if it is affected.

What it is: CVE-2026-16766 is a critical vulnerability in RRWO Catalyst::View::Wkhtmltopdf, published on 25 Jul 2026. 
Exploitation: There is no known exploitation of CVE-2026-16766 in the wild and no public exploit code.

Affected product: RRWO Catalyst::View::Wkhtmltopdf. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16766/ (Markdown: https://insights.sbomify.com/CVE-2026-16766/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16766
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16766
- OSV: https://osv.dev/vulnerability/CVE-2026-16766

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16766/
Summaries are generated and may contain mistakes; the official description above is the record.