CVE-2026-65321

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0%, top 41% 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
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

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

PyAthena prior to 3.35.4 contains a sql injection vulnerability that allows unauthenticated attackers to inject arbitrary SQL by exploiting improper quote-escaping in DefaultParameterFormatter.format(), which routes DELETE and CTAS statements to the _escape_hive function that backslash-escapes single quotes rather than doubling them. Because Athena and Trino do not treat backslashes as escape characters inside string literals, attacker-supplied input such as a single quote followed by SQL syntax causes the parser to terminate the string literal prematurely, enabling data exfiltration via UNION SELECT, execution of destructive statements, and attacker-controlled CTAS destination and content.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
59%
KEV
Not listed

Published

August 2, 2026

Last Modified

August 6, 2026

Advisory Details (6)

Auto-updated Aug 28, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
generic

PyAthena SQL Injection via DefaultParameterFormatter DELETE/CTAS | Advisories | VulnCheck

https://www.vulncheck.com/advisories/pyathena-sql-injection-via-defaultparameterformatter-delete-ctas
generic🟡 PoC Available

Rahul Karne — Cybersecurity Researcher

https://rahulkarne.com/#/cve/CVE-2026-65321
generic🟡 PoC Available

GitHub - rahulreddykarne/CVE-2026-65321-pyathena: SQL injection in PyAthena via DefaultParameterFormatter (CVE-2026-65321) · GitHub

https://github.com/rahulreddykarne/CVE-2026-65321-pyathena
github_commit Patch Available

commit 27901d12245e (pyathena-dev/PyAthena)

Patch available: pyathena-dev/PyAthena v3.35.4 (contains commit 27901d12245e)

https://github.com/pyathena-dev/PyAthena/commit/27901d12245ea722b3b4e211c60e2ade4e7c8efd
github Patch Available

SQL injection in DefaultParameterFormatter for DELETE and CTAS statements · Advisory · pyathena-dev/PyAthena · GitHub

https://github.com/laughingman7743/PyAthena/security/advisories/GHSA-xwj5-g6cv-4r5c
generic

GitHub - pyathena-dev/PyAthena: PyAthena is a Python DB API 2.0 (PEP 249) client for Amazon Athena. · GitHub

https://github.com/laughingman7743/PyAthena

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 55× 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-08-30 01:48 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 22:10 UTCEG score recompute
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 20:07 UTCEG score recompute
  6. 2026-08-26 19:13 UTCEG score recompute
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-25 15:52 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 17:46 UTCEG score recompute
  11. 2026-08-24 09:51 UTCEG score recompute
  12. 2026-08-23 00:31 UTCEG score recompute
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 02:43 UTCEG score recompute
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 01:15 UTCEG score recompute
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-19 19:01 UTCEG score recompute
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-18 15:50 UTCEG score recompute
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-17 17:01 UTCEG score recompute
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 15:36 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 30 more
  1. 2026-08-16 04:43 UTCEG score recompute
  2. 2026-08-15 02:44 UTCEG score recompute
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 01:21 UTCEG score recompute
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-12 16:31 UTCEG score recompute
  7. 2026-08-12 13:51 UTCEPSS rescore
  8. 2026-08-11 15:05 UTCEG score recompute
  9. 2026-08-11 00:34 UTCEG score recompute
  10. 2026-08-11 00:00 UTCEPSS rescore
  11. 2026-08-09 15:55 UTCEG score recompute
  12. 2026-08-09 13:47 UTCEPSS rescore
  13. 2026-08-08 18:10 UTCEG score recompute
  14. 2026-08-08 16:37 UTCEPSS rescore
  15. 2026-08-07 16:46 UTCEG score recompute
  16. 2026-08-06 15:34 UTCEG score recompute
  17. 2026-08-06 13:47 UTCEPSS rescore
  18. 2026-08-05 21:26 UTCEG score recompute
  19. 2026-08-05 19:17 UTCEPSS rescore
  20. 2026-08-05 19:17 UTCEPSS rescore
  21. 2026-08-04 16:04 UTCEG score recompute
  22. 2026-08-04 15:10 UTCEPSS rescore
  23. 2026-08-04 12:26 UTCEG score recompute
  24. 2026-08-04 10:39 UTCEPSS rescore
  25. 2026-08-03 17:40 UTCEG score recompute
  26. 2026-08-03 16:19 UTCEG score recompute
  27. 2026-08-03 11:28 UTCEG score recompute
  28. 2026-08-02 15:19 UTCEG score recompute
  29. 2026-08-02 15:13 UTCEG score recompute
  30. 2026-08-02 15:13 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-65321?
CVE-2026-65321 is a critical vulnerability published on August 2, 2026. PyAthena prior to 3.35.4 contains a sql injection vulnerability that allows unauthenticated attackers to inject arbitrary SQL by exploiting improper quote-escaping in DefaultParameterFormatter.format(), which routes DELETE and CTAS statements to the escapehive function that backslash-escapes single…
When was CVE-2026-65321 disclosed?
CVE-2026-65321 was first published in the National Vulnerability Database on August 2, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65321 actively exploited?
CVE-2026-65321 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 40.7% of all scored CVEs.
What is the CVSS score of CVE-2026-65321?
CVE-2026-65321 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-65321?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65321, 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

Explore the affected products and dependency analysis for CVE-2026-65321

Explore →

Is Your Infrastructure Affected by CVE-2026-65321?

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