JmespathApplication
CVE-2026-54133
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedjmespath.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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencejmespath.php versions before 2.9.1 contain a code injection vulnerability in the CompilerRuntime. When attacker-controlled JMESPath expressions are passed to the compiler, function names are emitted into generated PHP cache files without proper escaping, allowing injection of arbitrary executable PHP code that gets loaded and executed by the runtime.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
JmespathApplication
< 2.9.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify jmespath.php versionRun 'composer show jmespath/jmespath' or check the version listed in your composer.lock file under jmespath/jmespathAffected if The installed version is less than 2.9.1
-
Locate JMESPath usage in your codebaseSearch your source code for instantiation of 'Jmespath\CompilerRuntime' class - look for patterns like 'new CompilerRuntime()' or 'CompilerRuntime()'Affected if The CompilerRuntime class is being instantiated in your application code
-
Identify if expressions come from untrusted sourcesReview code paths where JMESPath expressions are passed to the CompilerRuntime; check if expression input originates from user request parameters, API input, file uploads, or external data sourcesAffected if Untrusted or user-controlled input flows into JMESPath expression evaluation via CompilerRuntime
-
Check for existing PHP cache filesSearch for .php cache files in directories referenced by CompilerRuntime (commonly under vendor/jmespath/jmespath or application cache directories); examine these files for suspicious PHP code or eval() patternsAffected if Cache files exist and contain unexpected or injected PHP code outside normal function name patterns
You are affected if jmespath.php version is below 2.9.1 AND your application uses CompilerRuntime with untrusted input, or if you find injected PHP code in JMESPath cache files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.9.1
Upgrade to jmespath.php version 2.9.1 or later. As an immediate workaround, ensure expressions are never evaluated by CompilerRuntime with untrusted input and configure applications to use AstRuntime instead.
2.9.1
- 1. Update the jmespath.php library to version 2.9.1 or later using your package manager (e.g., composer require mt山大/jmespath:^2.9.1)
- 2. Verify the installed version matches or exceeds 2.9.1 by running 'composer show mt山大/jmespath' or checking your lock file
- 3. If you cannot upgrade immediately, implement the workaround: switch from CompilerRuntime to AstRuntime for untrusted JMESPath expressions by replacing 'new \JmesPath\CompilerRuntime()' with 'new \JmesPath\AstRuntime()' in your code
- 4. Alternatively, disable JP_PHP_COMPILE by setting the environment variable or configuration to prevent the compiler from being used
- 5. After applying the fix, test your application to ensure JMESPath functionality continues to work correctly with both trusted and untrusted expressions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jmespath
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54133 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54133 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data