{"answers":{"affected":"2 open source packages ship an affected version, including mtdowling/jmespath.php. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54133 exists.","fix":"Upgrade mtdowling/jmespath.php to 2.9.1 or later.","what":"CVE-2026-54133 is a critical code injection vulnerability in jmespath.php, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54133 and fix it if it is affected.\n\nWhat it is: CVE-2026-54133 is a critical code injection vulnerability in jmespath.php, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54133 exists.\n\nAffected packages and fixed versions:\n- mtdowling/jmespath.php (Packagist): affected all versions; fixed in 2.9.1\n- mtdowling/jmespath.php (Packagist): affected all versions; fixed in 2.9.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54133/ (Markdown: https://insights.sbomify.com/CVE-2026-54133/index.md)","id":"CVE-2026-54133","markdown":"https://insights.sbomify.com/CVE-2026-54133/index.md","name":"CVE-2026-54133","record":{"aliases":["CLSA-2026-1793201827","GHSA-pcw8-m77r-2528","MINI-23f5-75j5-f23q","MINI-66wp-qgjx-pq38","MINI-7fv4-6f4g-vgm4","MINI-gg33-827h-29hg","MINI-vvcw-vjgq-32cx","MINI-xjq7-53q2-2765","MINI-xrmq-v97g-g799","ROOT-APP-COMPOSER-CVE-2026-54133"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"PHP JMESPath library","requires_auth":"none","summary":"Attackers can execute arbitrary PHP code via crafted JMESPath expressions when using the CompilerRuntime component in jmespath.php.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jmespath","vendor":"jmespath"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"jmespath.php has CompilerRuntime code injection via unescaped function names","id":"CVE-2026-54133","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"OctoPrint: File exfiltration possible via query parameters on upload endpoints","id":"CVE-2026-54134"},"packages":[{"ecosystem":"Packagist","fixed":["2.9.1"],"introduced":["0"],"last_affected":[],"package":"mtdowling/jmespath.php","purl":null,"source":"GHSA-pcw8-m77r-2528"},{"ecosystem":"Packagist","fixed":["2.9.1"],"introduced":["0"],"last_affected":[],"package":"mtdowling/jmespath.php","purl":"pkg:composer/mtdowling/jmespath.php","source":"GHSA-pcw8-m77r-2528"}],"prev":{"headline":"Windows Kernel Elevation of Privilege Vulnerability","id":"CVE-2026-54132"},"products":["jmespath.php"],"published":"2026-06-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-12","vendors":["jmespath"]},"summary":"Attackers can execute arbitrary PHP code via crafted JMESPath expressions when using the CompilerRuntime component in jmespath.php.","url":"https://insights.sbomify.com/CVE-2026-54133/"}