CVE-2026-62993

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
31(Track)
EG Risk 31/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity69% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

August 31, 2026

Last Modified

September 8, 2026

Advisory Details (6)

Auto-updated Aug 31, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v5.8.2

Patch available: smarty-php/smarty v5.8.2

https://github.com/smarty-php/smarty/releases/tag/v5.8.2
github_release Patch Available

v4.5.7

Patch available: smarty-php/smarty v4.5.7

https://github.com/smarty-php/smarty/releases/tag/v4.5.7
github_commit Patch Available

commit a1ccdb051802 (smarty-php/smarty)

Patch available: smarty-php/smarty v4.5.7 (contains commit a1ccdb051802)

https://github.com/smarty-php/smarty/commit/a1ccdb0518021a559b4066c37b76a42c86bbce90
github_commit Patch Available

commit 31e06fc087a8 (smarty-php/smarty)

Patch available: smarty-php/smarty v5.8.2 (contains commit 31e06fc087a8)

https://github.com/smarty-php/smarty/commit/31e06fc087a8b5a9b236c1e5dacc1c2850a2c115
github_pr Patch Available

Port security fixes from v5.8.2 to Smarty v4.

Patch available: smarty-php/smarty v4.5.7 (PR #1194 merged 2026-06-29)

https://github.com/smarty-php/smarty/pull/1194
github Patch Available

SSRF via redirect bypass of trusted_uri using {fetch} · Advisory · smarty-php/smarty · GitHub

Affected: 5.8.2. When a security policy is active, {fetch} now passes a stream context that

https://github.com/smarty-php/smarty/security/advisories/GHSA-cq55-c7wv-pxmq

Vendor Advisories for CVE-2026-62993(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(7 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
smarty33.1.47-2, 3.1.47-2+deb12u1, 3.1.48-1, 3.1.48-2——
smarty44.3.0-1 ... 4.5.5-1 (6 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
smarty33.1.48-2——
smarty44.5.5-1——
Debian:14(2)
PackageVulnerable rangeFixed inDependents
smarty33.1.48-2——
smarty44.5.5-1——
Packagist(1)
PackageVulnerable rangeFixed inDependents
smarty/smartyv2.6.24 ... v4.5.6 (72 versions)4.5.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-19 18:45 UTCEG score recompute
  3. 2026-09-18 19:46 UTCEG score recompute
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-17 20:47 UTCEG score recompute
  6. 2026-09-16 18:43 UTCEG score recompute
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 18:27 UTCEG score recompute
  10. 2026-09-13 19:38 UTCEG score recompute
  11. 2026-09-12 20:39 UTCEG score recompute
  12. 2026-09-11 21:40 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 09:37 UTCEPSS rescore
  15. 2026-09-10 22:41 UTCEG score recompute
  16. 2026-09-09 23:42 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-08 21:12 UTCEG score recompute
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-06 14:38 UTCEG score recompute
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-05 15:39 UTCEG score recompute
  23. 2026-09-05 15:31 UTCEPSS rescore
  24. 2026-09-04 16:39 UTCEG score recompute
  25. 2026-09-04 05:07 UTCEPSS rescore
Show 8 more
  1. 2026-09-02 18:37 UTCEG score recompute
  2. 2026-09-02 17:46 UTCEG score recompute
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 20:22 UTCEG score recompute
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-08-31 21:21 UTCEG score recompute
  7. 2026-08-31 21:07 UTCEG score recompute
  8. 2026-08-31 21:04 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62993?
CVE-2026-62993 is a medium vulnerability published on August 31, 2026. 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()…
When was CVE-2026-62993 disclosed?
CVE-2026-62993 was first published in the National Vulnerability Database on August 31, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62993 actively exploited?
CVE-2026-62993 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.0% of all scored CVEs.
What is the CVSS score of CVE-2026-62993?
CVE-2026-62993 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-62993?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62993, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62993

Explore →

Is Your Infrastructure Affected by CVE-2026-62993?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs