Skip to content
OpenAdvisories
Critical · 9.8 CVE-2026-54133 EUVD-2026-36431GHSA-pcw8-m77r-2528

jmespath.php has CompilerRuntime code injection via unescaped function names

Published Jun 12, 2026 · Updated Jun 12, 2026 · Assigned by GitHub_M

Description

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.

Affected products

VendorProductAffectedFixed
jmespath jmespath.php < 2.9.1 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling nextcloud-server-33 33.0.6-r9 —
Wolfi rolling ruby3.3-jmespath +1 No fix yet —

Affected packages

EcosystemPackageAffectedFixedRecord
Packagist mtdowling/jmespath.php < 2.9.1 2.9.1 GHSA-pcw8-m77r-2528

Advisories 1

References