Bug 2488378 (CVE-2026-54133) - CVE-2026-54133 jmespath.php: jmespath.php has CompilerRuntime code injection via unescaped function names
Summary: CVE-2026-54133 jmespath.php: jmespath.php has CompilerRuntime code injection ...
Keywords:
Status: NEW
Alias: CVE-2026-54133
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2489163 2489164 2489165
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-12 15:01 UTC by OSIDB Bzimport
Modified: 2026-06-16 12:30 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-06-12 15:01:24 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.