CVE-2026-54133
jmespath.php allows users to use JMESPath, software for …
jmespath.php allows users to use JMESPath, software for declaratively specifying how to extract elements from a JSON document, in PHP applications with PHP data structures. Versions prior to 2.9.1 can generate and execute attacker-controlled PHP code when `JmesPath\CompilerRuntime` is used with an attacker-controlled JMESPath expression. The compiler emits parsed JMESPath function names into generated PHP source without sufficient escaping. A crafted expression can cause the generated cache file to contain executable attacker-controlled PHP, which is then loaded by the compiler runtime. The issue is patched in `2.9.1` and later. As a workaround, disable `JP_PHP_COMPILE` and do not use `JmesPath\CompilerRuntime` with attacker-controlled expressions. Use the default `AstRuntime` for untrusted expressions. Applications that must continue accepting untrusted JMESPath expressions before upgrading should ensure those expressions are never evaluated by the compiler runtime.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/jmespath/jmespath.php/security/advisories/GHSA-pcw8-m77r-2528
- nvd.nist.gov/vuln/detail/CVE-2026-54133
- github.com/FriendsOfPHP/security-advisories/blob/master/mtdowling/jmespath.php/CVE-2026-54
- github.com/advisories/GHSA-pcw8-m77r-2528
- nvd.nist.gov/vuln/detail/CVE-2026-54133
- cve.org/CVERecord?id=CVE-2026-54133
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.