Vulnerability in mtdowling/jmespath.php (CVE-2026-54133)
Summary
Vulnerability in mtdowling/jmespath.php (CVE-2026-54133). Successful exploitation can lead to full system takeover. Exploitable via JP_PHP_COMPILE. Mitigation: upgrade to 2.9.1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54133 has been found in mtdowling/jmespath.php.
Attackers can target a specific entry point like JP_PHP_COMPILE over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade mtdowling/jmespath.php to 2.9.1 or later.
If unsure, ask your IT team or search "mtdowling/jmespath.php CVE-2026-54133" on the vendor's site.
CVE-2026-54133 (mtdowling/jmespath.php) — CWE-20 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: JP_PHP_COMPILE / CompilerRuntime / AstRuntime
Patched: 2.9.1 — apply immediately
Workaround: If you cannot upgrade immediately, disable JP_PHP_COMPILE and do not use JmesPath\CompilerRuntime with attacker-controlled expressions.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in mtdowling/jmespath.php. Attackers reach the vulnerable code path via JP_PHP_COMPILE without authentication.
Check the vendor advisory for the affected versions of mtdowling/jmespath.php. Attack surface: JP_PHP_COMPILE / CompilerRuntime / AstRuntime.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 2.9.1.
Workaround: If you cannot upgrade immediately, disable JP_PHP_COMPILE and do not use JmesPath\CompilerRuntime with attacker-controlled expressions.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mtdowling/jmespath.php' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mtdowling/jmespath.php' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mtdowling/jmespath.phpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
If you cannot upgrade immediately, disable `JP_PHP_COMPILE` and do not use `JmesPath\CompilerRuntime` with attacker-controlled expressions.パッチが適用されるまでの応急処置として、If you cannot upgrade immediately, disable
JP_PHP_COMPILEand do not useJmesPath\CompilerRuntimewith attacker-controlled expressions. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade mtdowling/jmespath.php to 2.9.1ステージング環境で 2.9.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com