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.
composer require mtdowling/jmespath.php:^2.9.4Is your project on an affected mtdowling/jmespath.php?
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
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.
| Version | Known advisories |
|---|---|
| mtdowling/jmespath.php 2.9.4 | None |
| mtdowling/jmespath.php 2.9.3 | None |
| mtdowling/jmespath.php 2.9.2 | None |
| mtdowling/jmespath.php 2.9.1 | None |
| mtdowling/jmespath.php 2.9.0 | CVE-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
- mtdowling/jmespath.php 2.10
- mtdowling/jmespath.php 2.8
- mtdowling/jmespath.php 2.7
- mtdowling/jmespath.php 2.6
- mtdowling/jmespath.php 2.5
- mtdowling/jmespath.php 1.1
- mtdowling/jmespath.php 1.0
- mtdowling/jmespath.php 0.4
- mtdowling/jmespath.php 0.3
- mtdowling/jmespath.php 0.2
- mtdowling/jmespath.php 0.1
- All mtdowling/jmespath.php advisories
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.