How many CVEs have patched _is_supported_upgrade?

1 published CVEs changed _is_supported_upgrade in aio-libs/aiohttp, in 1 distinct patches totalling 4 changed lines, between 2026 and 2026.

What is the latest CVE that changed _is_supported_upgrade?

CVE-2025-69224 (AIOHTTP's Unicode processing of header values could cause parsing discrepancies), published 2026-01-05, changed lines 241 to 243 of aiohttp/http_parser.py.

How does _is_supported_upgrade compare to the rest of aio-libs/aiohttp?

aio-libs/aiohttp has 42 CVEs with a located fix in total; 1 of them changed _is_supported_upgrade.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

aio-libs/aiohttp

Function

_is_supported_upgrade

Name: _is_supported_upgrade in aio-libs/aiohttp: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

aiohttp/http_parser.py

Last patched January 5, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

4

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

_is_supported_upgrade in aio-libs/aiohttp was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 4 lines in total.

aio-libs/aiohttp has 42 CVEs with a located fix in total, so 2% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed _is_supported_upgrade, newest first, with the lines each fix touched.

AIOHTTP's Unicode processing of header values could cause parsing discrepancies
CVE-2025-69224 · lines 241–243 · +3 −1
Medium · CVSS 6.3
EPSS 0.3%2026-01-05

Get an alert when the next CVE fix lands in aio-libs/aiohttp, with the patched functions.

Monitor aiohttp CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in aio-libs/aiohttp changed by the most CVE fixes.

parse_headers8 CVEs · aiohttp/http_parser.py feed_data7 CVEs · aiohttp/http_parser.py get_content_length6 CVEs · aiohttp/http_parser.py __init__5 CVEs · aiohttp/http_parser.py parse_message4 CVEs · aiohttp/http_parser.py post4 CVEs · aiohttp/web_request.py

All patched functions in aio-libs/aiohttp

Frequently asked questions

Common questions about CVE fixes to _is_supported_upgrade.

How many CVEs have patched _is_supported_upgrade?: 1 published CVEs changed _is_supported_upgrade in aio-libs/aiohttp, in 1 distinct patches totalling 4 changed lines, between 2026 and 2026.
What is the latest CVE that changed _is_supported_upgrade?: CVE-2025-69224 (AIOHTTP's Unicode processing of header values could cause parsing discrepancies), published 2026-01-05, changed lines 241 to 243 of aiohttp/http_parser.py.
How does _is_supported_upgrade compare to the rest of aio-libs/aiohttp?: aio-libs/aiohttp has 42 CVEs with a located fix in total; 1 of them changed _is_supported_upgrade.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track aio-libs/aiohttp CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing