CVE-2026-54133: jmespath.php has CompilerRuntime code injection via unescaped function names

Published Jun 12, 2026
·
Updated

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 JPPHPCOMPILE 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 Software

2 affected components
packagist/mtdowling/jmespath.php<2.9.1
jmespath Jmespath Php<2.9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade jmespath.php to a version that resolves this vulnerability.

    Fixed in 2.9.1
  2. Configuration

    Disable JP_PHP_COMPILE to prevent the compiler from generating and executing PHP code from JMESPath expressions.

    jmespath.php JP_PHP_COMPILE = disabled
  3. Configuration

    Use the default AstRuntime for untrusted JMESPath expressions and do not use JmesPath\CompilerRuntime with attacker-controlled expressions.

    jmespath.php runtime = AstRuntime
  4. Operational

    Ensure untrusted JMESPath expressions are never evaluated by JmesPath\CompilerRuntime until the application is upgraded to 2.9.1 or later.

Event History

Jun 12, 2026
CVE Published
via MITRE·01:56 PM
Data Sourced
via MITRE·01:56 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-54133?

The severity of CVE-2026-54133 is critical, rated 9.8 on the CVSS scale.

2

How do I fix CVE-2026-54133?

To fix CVE-2026-54133, upgrade to jmespath.php version 2.9.1 or later.

3

What is the risk associated with CVE-2026-54133?

CVE-2026-54133 has a risk score of 86, indicating a significant potential impact.

4

What type of vulnerability is CVE-2026-54133?

CVE-2026-54133 is classified as a code injection vulnerability due to unescaped function names.

5

Which versions of jmespath.php are affected by CVE-2026-54133?

Versions of jmespath.php prior to 2.9.1 are affected by CVE-2026-54133.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203