CVE-2026-69243

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% 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
Trending — 3 sources updated this week
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

A fix is available — apply it.

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.2, the HTTP parsers were vulnerable to a request smuggling attack relating to WebSocket upgrades. If using the server-side component, an attacker may be able to execute a request smuggling vulnerability using an edge case in the WebSocket upgrade procedure. A WebSocket upgrade request with a body could cause the parser to switch protocols before the complete request body was received, leaving trailing bytes to be handled as upgraded-protocol or pipelined data rather than normal HTTP body data. This issue is fixed in version 3.14.2.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

August 3, 2026

Last Modified

September 10, 2026

Advisory Details (3)

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

HTTP request smuggling via WebSocket upgrade · Advisory · aio-libs/aiohttp · GitHub

https://github.com/aio-libs/aiohttp/security/advisories/GHSA-mfx4-hv73-q22v
github_pr

[PR #13016/8ef76ab8 backport][3.14] Fix body reads after failed WS upgrade

Fix merged in aio-libs/aiohttp PR #13017 on 2026-06-30 — awaiting tagged release

https://github.com/aio-libs/aiohttp/pull/13017
github_commit

commit 6ae358f0983c (aio-libs/aiohttp)

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

https://github.com/aio-libs/aiohttp/commit/6ae358f0983c3f4d6f67692b2f8e65dc8e091c98

Patch Availability(11)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-aiohttp3.10.0-1 ... 3.9.5-1 (41 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-aiohttp3.10.0-1 ... 3.9.5-1 (33 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-aiohttp3.11.16-1 ... 3.14.1-5 (15 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-aiohttp3.11.16-1 ... 3.14.1-5 (14 versions)
PyPI(1)
PackageVulnerable rangeFixed inDependents
aiohttp0.1 ... 3.9.5 (308 versions)3.14.2

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 73× 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.

Showing the most recent 100 of 117 total refreshes for this CVE.

  1. 2026-09-19 03:43 UTCEG score recompute
  2. 2026-09-19 03:43 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 03:40 UTCEG score recompute
  5. 2026-09-18 03:40 UTCVendor advisory
  6. 2026-09-17 04:29 UTCEG score recompute
  7. 2026-09-17 04:29 UTCVendor advisory
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:18 UTCEG score recompute
  10. 2026-09-16 05:18 UTCVendor advisory
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 01:48 UTCVendor advisory
  13. 2026-09-13 18:46 UTCEG score recompute
  14. 2026-09-13 18:46 UTCVendor advisory
  15. 2026-09-12 19:35 UTCEG score recompute
  16. 2026-09-12 19:35 UTCVendor advisory
  17. 2026-09-11 20:24 UTCEG score recompute
  18. 2026-09-11 20:24 UTCVendor advisory
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 09:37 UTCEPSS rescore
  21. 2026-09-10 20:38 UTCEG score recompute
  22. 2026-09-10 20:38 UTCVendor advisory
  23. 2026-09-10 06:49 UTCVendor advisory
  24. 2026-09-09 06:42 UTCEG score recompute
  25. 2026-09-09 06:42 UTCVendor advisory
Show 75 more
  1. 2026-09-08 22:01 UTCEPSS rescore
  2. 2026-09-07 18:46 UTCEG score recompute
  3. 2026-09-07 18:46 UTCVendor advisory
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-06 08:38 UTCEG score recompute
  7. 2026-09-06 08:38 UTCVendor advisory
  8. 2026-09-05 15:31 UTCEPSS rescore
  9. 2026-09-05 09:27 UTCEG score recompute
  10. 2026-09-05 09:27 UTCVendor advisory
  11. 2026-09-04 10:16 UTCEG score recompute
  12. 2026-09-04 10:16 UTCVendor advisory
  13. 2026-09-04 05:07 UTCEPSS rescore
  14. 2026-09-03 08:32 UTCEG score recompute
  15. 2026-09-03 08:32 UTCVendor advisory
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 22:21 UTCEG score recompute
  18. 2026-09-01 22:21 UTCVendor advisory
  19. 2026-09-01 13:54 UTCEPSS rescore
  20. 2026-09-01 04:40 UTCEPSS rescore
  21. 2026-08-31 23:09 UTCVendor advisory
  22. 2026-08-30 21:08 UTCEG score recompute
  23. 2026-08-30 21:08 UTCVendor advisory
  24. 2026-08-30 19:17 UTCEPSS rescore
  25. 2026-08-30 01:22 UTCEPSS rescore
  26. 2026-08-29 21:56 UTCEG score recompute
  27. 2026-08-29 21:56 UTCVendor advisory
  28. 2026-08-28 21:42 UTCEPSS rescore
  29. 2026-08-27 21:56 UTCEG score recompute
  30. 2026-08-27 21:56 UTCVendor advisory
  31. 2026-08-26 22:45 UTCEG score recompute
  32. 2026-08-26 22:45 UTCVendor advisory
  33. 2026-08-26 14:47 UTCEPSS rescore
  34. 2026-08-25 23:33 UTCEG score recompute
  35. 2026-08-25 23:33 UTCVendor advisory
  36. 2026-08-25 13:49 UTCEPSS rescore
  37. 2026-08-25 00:22 UTCEG score recompute
  38. 2026-08-25 00:22 UTCVendor advisory
  39. 2026-08-24 01:10 UTCVendor advisory
  40. 2026-08-23 01:58 UTCEG score recompute
  41. 2026-08-23 01:58 UTCVendor advisory
  42. 2026-08-23 00:19 UTCEPSS rescore
  43. 2026-08-22 02:47 UTCEG score recompute
  44. 2026-08-22 02:47 UTCVendor advisory
  45. 2026-08-21 23:49 UTCEPSS rescore
  46. 2026-08-21 03:35 UTCEG score recompute
  47. 2026-08-21 03:35 UTCVendor advisory
  48. 2026-08-20 22:56 UTCEPSS rescore
  49. 2026-08-20 04:24 UTCEG score recompute
  50. 2026-08-20 04:24 UTCVendor advisory
  51. 2026-08-19 17:04 UTCEPSS rescore
  52. 2026-08-19 05:13 UTCEG score recompute
  53. 2026-08-19 05:13 UTCVendor advisory
  54. 2026-08-18 13:49 UTCEPSS rescore
  55. 2026-08-18 13:49 UTCEPSS rescore
  56. 2026-08-18 05:58 UTCEG score recompute
  57. 2026-08-18 05:58 UTCVendor advisory
  58. 2026-08-17 13:47 UTCEPSS rescore
  59. 2026-08-17 06:47 UTCEG score recompute
  60. 2026-08-17 06:47 UTCVendor advisory
  61. 2026-08-16 14:56 UTCEPSS rescore
  62. 2026-08-16 14:56 UTCEPSS rescore
  63. 2026-08-16 07:36 UTCEG score recompute
  64. 2026-08-16 07:36 UTCVendor advisory
  65. 2026-08-16 02:15 UTCEPSS rescore
  66. 2026-08-15 08:26 UTCEG score recompute
  67. 2026-08-15 08:26 UTCVendor advisory
  68. 2026-08-15 01:30 UTCEPSS rescore
  69. 2026-08-14 09:14 UTCEG score recompute
  70. 2026-08-14 09:14 UTCVendor advisory
  71. 2026-08-13 22:00 UTCEPSS rescore
  72. 2026-08-13 10:03 UTCEG score recompute
  73. 2026-08-12 13:51 UTCEPSS rescore
  74. 2026-08-12 10:52 UTCEG score recompute
  75. 2026-08-11 11:40 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-69243?
CVE-2026-69243 is a medium vulnerability published on August 3, 2026. AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.2, the HTTP parsers were vulnerable to a request smuggling attack relating to WebSocket upgrades. If using the server-side component, an attacker may be able to execute a request smuggling vulnerability…
When was CVE-2026-69243 disclosed?
CVE-2026-69243 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69243 actively exploited?
CVE-2026-69243 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 63.1% of all scored CVEs.
What is the CVSS score of CVE-2026-69243?
CVE-2026-69243 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-69243?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69243, 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-69243

Explore →

Is Your Infrastructure Affected by CVE-2026-69243?

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