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.1%, top 96% 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
4%
KEV
Not listed

Published

June 2, 2026

Last Modified

July 22, 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(6)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
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

(1 across 1 ecosystem)
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.

Data Freshness Timeline

(refreshed 15× in last 7d / 68× 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 135 total refreshes for this CVE.

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

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 July 22, 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 96.4% 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