Is mtdowling/jmespath.php 2.9 vulnerable?

Composer · 5 releases from 2.9.0 to 2.9.4 · latest mtdowling/jmespath.php is 2.10.0 · checked 18 Nov 2026

No known advisories in the last release

mtdowling/jmespath.php 2.9.4, the last 2.9 release, has no known advisories. 1 advisory affects earlier 2.9.x releases, so update to 2.9.4.

Update within 2.9:composer require mtdowling/jmespath.php:^2.9.4

Is your project on an affected mtdowling/jmespath.php?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 2.9.x, affecting earlier releases

  • CriticalCVE-2026-54133GHSA-pcw8-m77r-252818 Aug 2026

    jmespath.php has CompilerRuntime code injection via unescaped function names

    Affected
    <2.9.1
    Fixed in
    2.9.1

Every mtdowling/jmespath.php 2.9.x release

Affected: 2.9.0. 2.9.1 and later are not affected. Latest mtdowling/jmespath.php: 2.10.0.

VersionKnown advisories
mtdowling/jmespath.php 2.9.4None
mtdowling/jmespath.php 2.9.3None
mtdowling/jmespath.php 2.9.2None
mtdowling/jmespath.php 2.9.1None
mtdowling/jmespath.php 2.9.0CVE-2026-54133

Which of your client projects are still on mtdowling/jmespath.php 2.9?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact mtdowling/jmespath.php version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other mtdowling/jmespath.php versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.