CVE-2026-54274

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

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

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, if an attacker sends large incomplete websocket frame payloads, it may be possible to bypass the usual size limits on memory use. This vulnerability is fixed in 3.14.1.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
22.3%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 22, 2026
Patch available. Sources: github, github_commit.
github Patch Available

Incomplete websocket frame payloads bypass memory limits · Advisory · aio-libs/aiohttp · GitHub

https://github.com/aio-libs/aiohttp/security/advisories/GHSA-xcgm-r5h9-7989
github_commit

commit 14b6ee851fb1 (aio-libs/aiohttp)

Fix landed in aio-libs/aiohttp commit 14b6ee851fb1 — awaiting tagged release

https://github.com/aio-libs/aiohttp/commit/14b6ee851fb16ec199acb950de0c82d476799e7d

Vendor Advisories for CVE-2026-54274(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
aiohttp0.1 ... 3.9.5 (307 versions)3.14.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 45× 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-07 00:17 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 01:20 UTCEG score recompute
  7. 2026-07-05 12:13 UTCEG score recompute
  8. 2026-07-05 02:31 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 23:06 UTCEG score recompute
  11. 2026-07-04 10:00 UTCEG score recompute
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-03 20:22 UTCEG score recompute
  15. 2026-07-03 07:15 UTCEG score recompute
  16. 2026-07-02 17:31 UTCEG score recompute
  17. 2026-07-02 04:19 UTCEG score recompute
  18. 2026-07-01 15:12 UTCEG score recompute
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 02:05 UTCEG score recompute
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 12:57 UTCEG score recompute
  23. 2026-06-29 22:26 UTCEG score recompute
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 20 more
  1. 2026-06-29 09:17 UTCEG score recompute
  2. 2026-06-28 20:10 UTCEG score recompute
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 07:03 UTCEG score recompute
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-27 17:55 UTCEG score recompute▲ 0.90
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  10. 2026-06-26 18:44 UTCEG score recompute
  11. 2026-06-25 19:35 UTCEG score recompute
  12. 2026-06-25 13:49 UTCEPSS rescore
  13. 2026-06-24 20:25 UTCEG score recompute
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-23 21:33 UTCEPSS rescore
  16. 2026-06-23 21:33 UTCEPSS rescore
  17. 2026-06-23 18:52 UTCEG score recompute
  18. 2026-06-22 19:42 UTCEG score recompute▲ 6.60
  19. 2026-06-22 19:40 UTCNVD updateCVSS v3 → 6.6 · CVSS v4 → 6.6
  20. 2026-06-15 20:47 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54274?
CVE-2026-54274 is a high vulnerability published on June 15, 2026. AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, if an attacker sends large incomplete websocket frame payloads, it may be possible to bypass the usual size limits on memory use. This vulnerability is fixed in 3.14.1.
When was CVE-2026-54274 disclosed?
CVE-2026-54274 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54274 actively exploited?
CVE-2026-54274 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54274?
CVE-2026-54274 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-54274?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54274, 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-54274

Explore →

Is Your Infrastructure Affected by CVE-2026-54274?

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

Start Free Scan →Browse All CVEs