Snappy: Binary path is never shell-escaped due to an inverted is_executable check
Published 21 May 2026 · Updated 10 Sept 2026
Is your project on an affected KnpLabs/knp-snappy?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <1.7.1
- Fixed in
- 1.7.1
composer require KnpLabs/knp-snappy:^1.7.1Details
Impact
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.
Proof of concept:
$pdf = new Knp\Snappy\Pdf(‘wkhtmltopdf; touch /tmp/snappy_rce’); $pdf->generate(‘https://example.com’, ‘/tmp/out.pdf’); // /tmp/snappy_rce is created.
Impact: command execution as the PHP process when the binary path is attacker-influenced. Even in deployments where the binary is hard-coded, this is a defensive-in-depth regression: downstream packages reasonably assume Snappy shell-escapes the binary because the code looks like it does.
Patches
The version 1.7.1 will resolve this security advisory.
Workarounds
Before calling the constructor, ensure \is_executable($path) is truthy.
// Bad example
$pdf = new Knp\Snappy\Pdf('/path/to/binary');// Better example
$pathToBinary = '/path/to/binary';
if (!\is_executable($pathToBinary)) {
throw new \RuntimeException();
}
$pdf = new Knp\Snappy\Pdf('/path/to/binary');Is GHSA-vpr4-p6fq-85jc in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected KnpLabs/knp-snappy, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.