Is mtdowling/jmespath.php 0.1 vulnerable?
Composer · 1 release from 0.1.0 to 0.1.0 · latest mtdowling/jmespath.php is 2.10.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. mtdowling/jmespath.php 0.1.0, the last 0.1 release, is affected by 1 known security advisory (1 critical), including CVE-2026-54133. Upgrade to 2.9.1 or later to fix all of them.
composer require mtdowling/jmespath.php:^2.9.1Is 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
Advisories affecting mtdowling/jmespath.php 0.1.0
jmespath.php has CompilerRuntime code injection via unescaped function names
- Affected
- <2.9.1
- Fixed in
- 2.9.1
Which of your client projects are still on mtdowling/jmespath.php 0.1?
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 0.4
- mtdowling/jmespath.php 0.3
- mtdowling/jmespath.php 0.2
- mtdowling/jmespath.php 2.10
- mtdowling/jmespath.php 2.9
- 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
- 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.