{"answers":{"affected":"2 open source packages ship an affected version, including twig/twig. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-46633 in the wild and no public exploit code.","fix":"Upgrade twig/twig to 3.26.0 or later.","what":"CVE-2026-46633 is a high-severity code injection vulnerability in twigphp Twig, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46633 and fix it if it is affected.\n\nWhat it is: CVE-2026-46633 is a high-severity code injection vulnerability in twigphp Twig, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-46633 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- twig/twig (Packagist): affected all versions; fixed in 3.26.0\n- twig/twig (Packagist): affected all versions; fixed in 3.26.0\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-46633/ (Markdown: https://insights.sbomify.com/CVE-2026-46633/index.md)","id":"CVE-2026-46633","markdown":"https://insights.sbomify.com/CVE-2026-46633/index.md","name":"CVE-2026-46633","record":{"aliases":["DEBIAN-CVE-2026-46633","GHSA-7p85-w9px-jpjp","ROOT-APP-COMPOSER-CVE-2026-46633","UBUNTU-CVE-2026-46633"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP template engine","requires_auth":"low_privilege","summary":"Attackers can inject arbitrary PHP code via crafted template names in Twig templates, leading to remote code execution.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"twig","vendor":"symfony"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Twig is a template language for PHP. Prior to 3.26.0, Compiler::string() does not escape single quotes when a template name from a {% use %} tag is placed inside a PHP single-quoted string literal, allowing a crafted template name to terminate the string and inject arbitrary PHP expressions into the compiled cache file. This issue is fixed in version 3.26.0.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Twig: PHP code injection via `{% use %}` template name","id":"CVE-2026-46633","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Twig: `template_from_string()` escapes a SourcePolicy-driven sandbox via synthesized template name","id":"CVE-2026-46634"},"packages":[{"ecosystem":"Packagist","fixed":["3.26.0"],"introduced":["0"],"last_affected":[],"package":"twig/twig","purl":null,"source":"GHSA-7p85-w9px-jpjp"},{"ecosystem":"Packagist","fixed":["3.26.0"],"introduced":["0"],"last_affected":[],"package":"twig/twig","purl":"pkg:composer/twig/twig","source":"GHSA-7p85-w9px-jpjp"}],"prev":{"headline":"Twig: Unbounded formatter memoisation in twig/intl-extra keyed on template-controlled arguments","id":"CVE-2026-46629"},"products":["Twig"],"published":"2026-07-14","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2018-13818","kev_date_added":null,"published":"2018-07-10"},{"cvss_score":8.7,"headline":"Twig: Arbitrary PHP code execution via `_self.(\u003cstring\u003e)` macro-reference compilation","id":"CVE-2026-46640","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":8.7,"headline":"Twig 2.16.x \u0026 3.9.0-3.25.x Sandbox Bypass via SourcePolicyInterface","id":"CVE-2026-24425","kev_date_added":null,"published":"2026-05-20"},{"cvss_score":8.6,"headline":"Twig has a possible sandbox bypass","id":"CVE-2024-45411","kev_date_added":null,"published":"2024-09-09"},{"cvss_score":7.7,"headline":"Twig: `template_from_string()` escapes a SourcePolicy-driven sandbox via synthesized template name","id":"CVE-2026-46634","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2001-1537","kev_date_added":null,"published":"2005-07-14"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-16","vendors":["twigphp"]},"summary":"Attackers can inject arbitrary PHP code via crafted template names in Twig templates, leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2026-46633/"}