Vulnerability · medium · CVSS 6.3
aiohttp header hardening for CVE-2025-69224 leaves response parser unpatched
Tier B · Patch this week – Put it in the sprint
Who’s exposed: aiohttp users with affected versions handling non-ASCII headers
Tier B because: Core infrastructure or popular tool AND remote, no login
Reach
Attack
Damage
Fix
Popular tool · Remote, no login
The Brief
- aiohttp fixed CVE-2025-69224 in January 2026, rated low, for Unicode processing of header values that could cause parsing discrepancies.
- The fix rejects non-ASCII characters in some headers, but it was applied only to the request parser.
- The response parser is not covered by the header hardening, according to the post.
Why it matters
If the response parser has the same header-parsing discrepancy, applications relying on aiohttp's fix may remain exposed through responses it handles.
The checklist behind the tier
Checklist · 3 of 10 yes
| Yes | Hits tech teams | aiohttp is a Python HTTP library that developers build web services with. |
| No | Core infrastructure | A single Python framework, not software nearly every team runs. |
| Yes | Popular tool | aiohttp is a widely used Python async HTTP framework with many dependent projects. |
| No | Exploited in the wild | Open Source Security post describes a live-proven flaw but reports no observed attacks. |
| No | Public exploit | Open Source Security post does not say exploit code or a PoC is published. |
| Yes | Remote, no login | CVSSCVE-2025-69224: CVSS 6.3 – network, no privileges, no user interaction |
| No | Full takeover | CVSSCVSS: no CVE has both high confidentiality and integrity impact |
| No | Secrets exposed | Open Source Security post reports no stolen or exposed credentials, configs or data. |
| No | Supply chain | Open Source Security post describes a parser flaw, not a compromised package or pipeline. |
| No | No fix yet | GitHub AdvisoryGitHub Advisory: aiohttp fixed in 3.13.3 |
The official record
From CVE.org, CISA’s Known Exploited Vulnerabilities catalog, FIRST EPSS and the GitHub Advisory Database. Where these answer a checklist fact, they win over the reporting.
CVE-2025-69224 ↗CVSS 6.3 medium AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
AIOHTTP's Unicode processing of header values could cause parsing discrepancies
- Exploited
- Not in CISA’s exploited catalog
- EPSS
- <1% chance of exploitation in the next 30 days · higher than 16% of all CVEs
- Fix
- aiohttp (pip) fixed in 3.13.3
- Weakness
- CWE-444
Timeline
Source
aiohttp: half a fix — the CVE-2025-69224 header hardening covers the request parser, not the response parser (live-proven, low) ↗ Open Source Security · 11h ago
First seen · 1 source · Full story page · How tiers are decided