CVE-2026-34993

HIGHNVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 93% 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
Trending — Patch released this week
7.3EG
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.3Exploit: None knownExposed: 0

A fix is available — apply it.

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.14.0, using `CookieJar.load()` with untrusted input may allow arbitrary code execution. Most applications using this function will be doing so with the user's own data, so this is unlikely to affect many applications. Version 3.14.0 patches the issue. If an application does allow attacker controlled files to be loaded, a workaround on older releases would be to sanitize the files before loading.

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

Published

June 2, 2026

Last Modified

September 4, 2026

Advisory Details (2)

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

Deserialization of Untrusted Data in aiohttp · Advisory · aio-libs/aiohttp · GitHub

https://github.com/aio-libs/aiohttp/security/advisories/GHSA-jg22-mg44-37j8
github_commit

commit dcf40f30637e (aio-libs/aiohttp)

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

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

Vendor Advisories for CVE-2026-34993(20)

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

Patch Availability(19)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpython-aiohttp-0:3.14.3-1.el9pc2026-09-03redhat
redhatpython3.12-aiohttp-0:3.14.3-1.el9pc2026-09-03redhat
redhatpython3.12-pulpcore-0:3.73.30-3.el9pc2026-09-03redhat
redhatrhelai3/disk-image-cuda-rhel9:17882903142026-09-01redhat
redhatrhelai3/bootc-gcp-cuda-rhel9:17882739772026-09-01redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatrhaiis/model-opt-cuda-rhel9:17876011592026-08-25redhat
redhatautomation-controller-0:4.6.32-1.el9ap2026-08-24redhat
redhatautomation-controller-0:4.7.16-1.el9ap2026-08-24redhat
redhatdiscovery/discovery-server-rhel9:17866385732026-08-13redhat
redhatpython3.12-aiohttp-0:3.14.1-2.el9ap2026-08-04redhat
redhatansible-automation-platform-26/lightspeed-rhel9:17857753602026-08-04redhat
redhatansible-automation-platform-25/ee-supported-rhel8:17854296572026-08-04redhat
redhatansible-automation-platform-27/lightspeed-chatbot-rhel9:17854267342026-08-04redhat
redhatmta/mta-solution-server-rhel9:17841098832026-07-21redhat
redhatrhoai/odh-ta-lmes-job-rhel9:17830911752026-07-21redhat
redhatrhoai/odh-trustyai-garak-lls-provider-dsp-rhel9:17824723742026-07-09redhat
redhatrhoai/odh-trustyai-garak-lls-provider-dsp-rhel9:17821339072026-07-01redhat
redhatrhoai/odh-training-rocm62-torch25-py311-rhel9:17800691812026-06-10redhat

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 (32 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-aiohttp3.11.16-1 ... 3.14.1-4 (14 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-aiohttp3.11.16-1 ... 3.13.5-1 (8 versions)3.14.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
aiohttp0.1 ... 3.9.5 (306 versions)3.14.0—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 16× in last 7d / 93× 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 266 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-34993?
CVE-2026-34993 is a high vulnerability published on June 2, 2026. AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.14.0, using CookieJar.load() with untrusted input may allow arbitrary code execution. Most applications using this function will be doing so with the user's own data, so this is unlikely to affect…
When was CVE-2026-34993 disclosed?
CVE-2026-34993 was first published in the National Vulnerability Database on June 2, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34993 actively exploited?
CVE-2026-34993 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 92.5% of all scored CVEs.
What is the CVSS score of CVE-2026-34993?
CVE-2026-34993 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-34993?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34993, 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-34993

Explore →

Is Your Infrastructure Affected by CVE-2026-34993?

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

Start Free Scan →Browse All CVEs