CVE-2026-45073

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% 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, nvd
7.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.3Exploit: NoneExposed: 0

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

Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 5.4.52, 6.4.40, 7.4.12, and 8.0.12, PdoAdapter::doClear() builds a DELETE statement using a namespace derived from the caller-supplied $prefix without binding or escaping it, allowing a caller able to influence $prefix to break out of the LIKE literal and alter query semantics or deletion scope. This issue is fixed in versions 5.4.52, 6.4.40, 7.4.12, and 8.0.12.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity73% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
33.5%
KEV
Not listed

Published

May 27, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Jul 15, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

SQL Injection in PdoAdapter::doClear() via Unsanitized $prefix · Advisory · symfony/symfony · GitHub

https://github.com/symfony/symfony/security/advisories/GHSA-6qh9-h6wf-jgqc
github_release Patch Available

v8.0.12

Patch available: symfony/symfony v8.0.12

https://github.com/symfony/symfony/releases/tag/v8.0.12
github_release Patch Available

v7.4.12

Patch available: symfony/symfony v7.4.12

https://github.com/symfony/symfony/releases/tag/v7.4.12
github_release Patch Available

v6.4.40

Patch available: symfony/symfony v6.4.40

https://github.com/symfony/symfony/releases/tag/v6.4.40
github_release Patch Available

v5.4.52

Patch available: symfony/symfony v5.4.52

https://github.com/symfony/symfony/releases/tag/v5.4.52
github_commit Patch Available

commit ec50b799d79e (symfony/symfony)

Patch available: symfony/symfony v5.4.52 (contains commit ec50b799d79e)

https://github.com/symfony/symfony/commit/ec50b799d79ebe24561f29351c1efcb6da95c9b1

Vendor Advisories for CVE-2026-45073(1)

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

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFixed inDependents
symfony/cachev8.0.0 ... v8.0.9 (10 versions)8.0.12
symfony/symfonyv8.0.0 ... v8.0.9 (12 versions)8.0.12

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 11× 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-07-23 03:16 UTCEG score recompute 1.00
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 16:23 UTCNVD updateCVSS v3 → 7.3 · severity → HIGH
  10. 2026-07-14 18:35 UTCEG score recompute 6.30
  11. 2026-07-14 18:35 UTCMITRE cvelistV5CVSS v3 → 6.3 · CVSS v4 → 6.3
  12. 2026-06-14 23:18 UTCEPSS rescore
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-05-27 21:35 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-45073?
CVE-2026-45073 is a high vulnerability published on May 27, 2026. Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 5.4.52, 6.4.40, 7.4.12, and 8.0.12, PdoAdapter::doClear() builds a DELETE statement using a namespace derived from the caller-supplied $prefix without binding or escaping it, allowing a caller…
When was CVE-2026-45073 disclosed?
CVE-2026-45073 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45073 actively exploited?
CVE-2026-45073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45073?
CVE-2026-45073 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-45073?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45073, 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-45073

Explore →

Is Your Infrastructure Affected by CVE-2026-45073?

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