mtdowling/jmespath.php vulnerabilities
Declaratively specify how to extract elements from a JSON document
- Registry
- Composer
- Latest
- 2.10.0
- License
- MIT
1 known advisory
The latest version, 2.10.0, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require mtdowling/jmespath.php:^2.10.0Is 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
Security advisories for mtdowling/jmespath.php
jmespath.php has CompilerRuntime code injection via unescaped function names
- Affected
- <2.9.1
- Fixed in
- 2.9.1
Is your mtdowling/jmespath.php version vulnerable?
- mtdowling/jmespath.php 2.10No known advisories in 2.10.0
- mtdowling/jmespath.php 2.9No known advisories in 2.9.4
- mtdowling/jmespath.php 2.81 advisory in 2.8.0
- mtdowling/jmespath.php 2.71 advisory in 2.7.0
- mtdowling/jmespath.php 2.61 advisory in 2.6.1
- mtdowling/jmespath.php 2.51 advisory in 2.5.0
- mtdowling/jmespath.php 1.11 advisory in 1.1.1
- mtdowling/jmespath.php 1.01 advisory in 1.0.0
- mtdowling/jmespath.php 0.41 advisory in 0.4.0
- mtdowling/jmespath.php 0.31 advisory in 0.3.0
- mtdowling/jmespath.php 0.21 advisory in 0.2.0
- mtdowling/jmespath.php 0.11 advisory in 0.1.0
Which of your client projects still run an old mtdowling/jmespath.php?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.