# CVE-2026-46643: Snappy: Binary path is never shell-escaped due to an inverted is_executable check

> Attackers can execute arbitrary commands if the binary path is influenced by user-controlled configuration or environment variables due to improper shell escaping.

- **Severity:** High 7.5 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** GHSA-vpr4-p6fq-85jc

## What is CVE-2026-46643?

CVE-2026-46643 is a high-severity command injection vulnerability in KnpLabs snappy, published on 10 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Snappy is a PHP library allowing thumbnail, snapshot or PDF generation from a url or a html page. Prior to version 1.7.1, on POSIX, escapeshellarg(‘/usr/bin/wkhtmltopdf’) returns the literal string ‘/usr/bin/wkhtmltopdf’ with the single-quote characters included. is_executable() then looks for a file whose actual name contains those quote characters, which essentially never exists. The safe branch is dead code and $command always falls through to the raw, unescaped value. The rest of the arguments (options, input, output) are escaped correctly, so injection has to land in the binary string itself. That happens whenever the binary path is sourced from configuration that is user-influenced, derived from environment variables that ultimately come from request data, or concatenated with any user-controlled fragment. This issue has been patched in version 1.7.1.

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

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

2 open source packages ship an affected version, including KnpLabs/knp-snappy.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `KnpLabs/knp-snappy` | Packagist | All versions | 1.7.1 |
| `KnpLabs/knp-snappy` | Packagist | All versions | 1.7.1 |

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

Upgrade KnpLabs/knp-snappy to 1.7.1 or later.

## Is CVE-2026-46643 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46643 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46643 is a high-severity command injection vulnerability in KnpLabs snappy, published on 10 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46643 exists.

Affected packages and fixed versions:
- KnpLabs/knp-snappy (Packagist): affected all versions; fixed in 1.7.1
- KnpLabs/knp-snappy (Packagist): affected all versions; fixed in 1.7.1

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-46643/ (Markdown: https://insights.sbomify.com/CVE-2026-46643/index.md)
```

## Sources

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

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