Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-vpr4-p6fq-85jc

Snappy: Binary path is never shell-escaped due to an inverted is_executable check

CVSS 7.5 HighEPSS 0.0020 · 9th percentile

Published by the GitHub Advisory Database at 21 May 2026, 20:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
KnpLabs/knp-snappyPackagist<1.7.11.7.1
Identifiers
GHSA-vpr4-p6fq-85jc · CVE-2026-46643 · PKSA-13wp-m816-mvdd
Weakness (CWE)
CWE-78
Tags
Published
21 May 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The knp-snappy Packagist package (versions before 1.7.1) does not shell-escape the binary path, because an inverted is_executable check causes the escaping branch to be skipped on POSIX systems. An attacker who can influence the binary path, for example through configuration or environment values derived from request data, could inject shell commands and run them as the PHP process. The fix is to upgrade to version 1.7.1, which the source says resolves this issue; the source also suggests a workaround of ensuring the path passes is_executable before the constructor is called.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0020, the 9th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:58 UTC First seen by agentprime
  2. 31 Oct 2026, 13:58 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.