{"answers":{"affected":"4 open source packages ship an affected version, including smarty/smarty.","exploited":"There is no known exploitation of CVE-2026-62993 in the wild and no public exploit code.","fix":"Upgrade smarty/smarty to a fixed version for your release line: 4.5.7 or 5.8.2.","what":"CVE-2026-62993 is a medium-severity server-side request forgery vulnerability in smarty-php smarty, published on 31 Aug 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-62993 and fix it if it is affected.\n\nWhat it is: CVE-2026-62993 is a medium-severity server-side request forgery vulnerability in smarty-php smarty, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-62993 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- smarty/smarty (Packagist): affected all versions; fixed in 4.5.7\n- smarty/smarty (Packagist): affected all versions; fixed in 4.5.7\n- smarty/smarty (Packagist): affected from 5.0.0; fixed in 5.8.2\n- smarty/smarty (Packagist): affected from 5.0.0; fixed in 5.8.2\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-62993/ (Markdown: https://insights.sbomify.com/CVE-2026-62993/index.md)","id":"CVE-2026-62993","markdown":"https://insights.sbomify.com/CVE-2026-62993/index.md","name":"CVE-2026-62993","record":{"aliases":["DEBIAN-CVE-2026-62993","GHSA-cq55-c7wv-pxmq","UBUNTU-CVE-2026-62993"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"PHP template engine","requires_auth":"none","summary":"Attackers can bypass trusted URI restrictions in Smarty's fetch function via open redirects, enabling server-side request forgery to access internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to 4.5.7 and 5.8.2, depending on the release line, Smarty's {fetch} handling in libs/plugins/function.fetch.php and src/FunctionHandler/Fetch.php used Security::isTrustedUri() to validate only the initial remote URL against trusted_uri when a security policy was active. For resources handled by file_get_contents(), including HTTPS URLs, PHP followed HTTP redirects by default. An attacker who could supply or influence a fetch target and had an open redirect on a trusted host could redirect the request to an attacker-chosen internal endpoint, bypass the trusted_uri allowlist, and perform server-side request forgery. This issue is fixed in versions 4.5.7 and 5.8.2.","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":"Smarty: SSRF via redirect bypass of trusted_uri using {fetch}","id":"CVE-2026-62993","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":4,"n_references":6,"next":{"headline":"CoreDNS `k8s_external` headless AXFR can emit an empty transfer batch that panics the `transfer` plugin","id":"CVE-2026-62994"},"packages":[{"ecosystem":"Packagist","fixed":["4.5.7"],"introduced":["0"],"last_affected":[],"package":"smarty/smarty","purl":null,"source":"GHSA-cq55-c7wv-pxmq"},{"ecosystem":"Packagist","fixed":["4.5.7"],"introduced":["0"],"last_affected":[],"package":"smarty/smarty","purl":"pkg:composer/smarty/smarty","source":"GHSA-cq55-c7wv-pxmq"},{"ecosystem":"Packagist","fixed":["5.8.2"],"introduced":["5.0.0"],"last_affected":[],"package":"smarty/smarty","purl":null,"source":"GHSA-cq55-c7wv-pxmq"},{"ecosystem":"Packagist","fixed":["5.8.2"],"introduced":["5.0.0"],"last_affected":[],"package":"smarty/smarty","purl":"pkg:composer/smarty/smarty","source":"GHSA-cq55-c7wv-pxmq"}],"prev":{"headline":"Smarty: Symlink path traversal out of trusted directories","id":"CVE-2026-62992"},"products":["smarty"],"published":"2026-08-31","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-02","vendors":["smarty-php"]},"summary":"Attackers can bypass trusted URI restrictions in Smarty's fetch function via open redirects, enabling server-side request forgery to access internal resources.","url":"https://insights.sbomify.com/CVE-2026-62993/"}