# aiohttp: half a fix — the CVE-2025-69224 header hardening covers the request parser, not the response parser (live-proven, low)

Source: [Open Source Security](https://seclists.org/oss-sec/2026/q4/811) · 2026-11-22 · Security
Page: https://themorning.dev/story/aiohttp-half-a-fix-the-cve-2025-69224-header-hardening-covers-the-request-parser-2d2df2b16681ac7d
Kind: security · Impact: low

## In 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.

## CVEs

- CVE-2025-69224

## Timeline

- 2026-11-22: Post on oss-security says the CVE-2025-69224 fix covers only the request parser, not the response parser

## Coverage

- [aiohttp: half a fix — the CVE-2025-69224 header hardening covers the request parser, not the response parser (live-proven, low)](https://seclists.org/oss-sec/2026/q4/811) — Open Source Security, 2026-11-22

Tags: aiohttp, python, security, http, cve

---

Brief generated by AI (claude-haiku-5-5) from the reporting listed under Coverage. Headlines belong to their publishers. The Morning Dev – https://themorning.dev
