CVE-2026-54280

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 80% 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, payload resources are not closed correctly when a client disconnects in the middle of a write. If a payload is using an open file or similar limited resource, then an attacker may be able to cause resource starvation temporarily until garbage collection or similar closes the file. This vulnerability is fixed in 3.14.1.

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

Published

June 15, 2026

Last Modified

June 26, 2026

Advisory Details (2)

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

Payload Response Resources Are Not Closed After Mid-Body Disconnect · Advisory · aio-libs/aiohttp · GitHub

https://github.com/aio-libs/aiohttp/security/advisories/GHSA-9x8q-7h8h-wcw9
github_commit

commit a762eda5242f (aio-libs/aiohttp)

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

https://github.com/aio-libs/aiohttp/commit/a762eda5242f6490d6ba667533193f8b473ad587

Vendor Advisories for CVE-2026-54280(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 / 40× 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-05 22:38 UTCEG score recompute
  7. 2026-07-05 10:26 UTCEG score recompute
  8. 2026-07-05 02:31 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 22:11 UTCEG score recompute
  11. 2026-07-04 09:59 UTCEG score recompute
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-03 20:45 UTCEG score recompute
  15. 2026-07-03 08:30 UTCEG score recompute
  16. 2026-07-02 20:06 UTCEG score recompute
  17. 2026-07-02 07:54 UTCEG score recompute
  18. 2026-07-01 19:43 UTCEG score recompute
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 07:32 UTCEG score recompute
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 19:21 UTCEG score recompute
  23. 2026-06-30 07:10 UTCEG score recompute
  24. 2026-06-29 18:55 UTCEG score recompute
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 15 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-29 06:43 UTCEG score recompute▲ 5.80
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  8. 2026-06-26 01:13 UTCEG score recompute
  9. 2026-06-25 13:49 UTCEPSS rescore
  10. 2026-06-24 14:05 UTCEPSS rescore
  11. 2026-06-23 21:33 UTCEPSS rescore
  12. 2026-06-23 21:33 UTCEPSS rescore
  13. 2026-06-22 19:42 UTCEG score recompute▲ 1.70
  14. 2026-06-22 19:40 UTCNVD updateCVSS v3 → 1.7 · CVSS v4 → 1.7
  15. 2026-06-15 20:47 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54280?
CVE-2026-54280 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, payload resources are not closed correctly when a client disconnects in the middle of a write. If a payload is using an open file or similar limited resource, then an attacker may be able to cause…
When was CVE-2026-54280 disclosed?
CVE-2026-54280 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-54280 actively exploited?
CVE-2026-54280 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54280?
CVE-2026-54280 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-54280?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54280, 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-54280

Explore →

Is Your Infrastructure Affected by CVE-2026-54280?

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

Start Free Scan →Browse All CVEs