CVE-2026-69244

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% 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
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: 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.3, an out-of-bounds heap read could occur in the C response parser while building an error message for a malformed response. An attacker controlled server, or possibly an accidental response, could trigger a DoS in the client. The vulnerable path was error message construction in aiohttp/_http_parser.pyx, where an llhttp error-position pointer was used to build a snippet for malformed chunked responses and malformed request or response bytes at the buffer end. This issue is fixed in version 3.14.3.

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

Published

August 3, 2026

Last Modified

September 10, 2026

Advisory Details (3)

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

Out-of-bounds heap read in C HTTP response parser may lead to DoS · Advisory · aio-libs/aiohttp · GitHub

https://github.com/aio-libs/aiohttp/security/advisories/GHSA-cq5v-8q36-5273
github_pr

[PR #13222/f4866933 backport][3.14] Build C parser error message from bounded buffer slice

Fix merged in aio-libs/aiohttp PR #13223 on 2026-07-22 — awaiting tagged release

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

commit 49f65d541503 (aio-libs/aiohttp)

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

https://github.com/aio-libs/aiohttp/commit/49f65d54150397892f7bcc4aae887767d51c322d

Vendor Advisories for CVE-2026-69244(17)

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

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17881858992026-09-08redhat
redhatpython3.12-aiohttp-0:3.14.3-1.el9pc2026-09-03redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17881902242026-09-03redhat
redhatpython-aiohttp-0:3.14.3-1.el9pc2026-09-03redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17881903822026-09-03redhat
redhatpython3.12-pulpcore-0:3.73.30-3.el9pc2026-09-03redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatpython3.12-aiohttp-0:3.14.3-1.el9ap2026-08-24redhat
redhatansible-automation-platform-27/lightspeed-rhel9:17872175312026-08-24redhat
redhatansible-automation-platform-26/lightspeed-rhel9:17872440792026-08-24redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17872293852026-08-24redhat
redhatansible-automation-platform/ee-minimal-rhel9:17869422322026-08-17redhat
redhatansible-automation-platform/ee-minimal-rhel8:17869712882026-08-17redhat
redhatdiscovery/discovery-server-rhel9:17866385732026-08-13redhat

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 (309 versions)3.14.3—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 91× 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 140 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-69244?
CVE-2026-69244 is a high vulnerability published on August 3, 2026. AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.3, an out-of-bounds heap read could occur in the C response parser while building an error message for a malformed response. An attacker controlled server, or possibly an accidental response, could trigger…
When was CVE-2026-69244 disclosed?
CVE-2026-69244 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-69244 actively exploited?
CVE-2026-69244 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 77.2% of all scored CVEs.
What is the CVSS score of CVE-2026-69244?
CVE-2026-69244 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-69244?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69244, 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-69244

Explore →

Is Your Infrastructure Affected by CVE-2026-69244?

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

Start Free Scan →Browse All CVEs