Bug 2427253 (CVE-2025-69225)

Summary:	CVE-2025-69225 aiohttp: aiohttp: Request smuggling vulnerability via non-ASCII decimals in Range header
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	adudiak, alinfoot, anpicker, anthomas, bbrownin, bdettelb, bparees, carogers, caswilli, dfreiber, doconnor, drow, dtrifiro, dymurray, ehelms, erezende, ggainey, haoli, hasun, hkataria, ibolton, jajackso, jburrell, jcammara, jdobes, jfula, jkoehler, jmatthew, jmitchel, jmontleo, jneedle, jowilson, jsamir, juwatts, jwong, kaycoth, kegrant, koliveir, kshier, lphiri, mabashia, mhulan, nmoumoul, nyancey, omaciel, ometelka, orabin, osousa, pakotvan, pbohmill, pbraun, pcreech, pgaikwad, ptisnovs, rbryant, rchan, rjohnson, shvarugh, simaishi, slucidi, smallamp, smcdonal, sseago, stcannon, sthirugn, syedriko, teagle, tfister, thavo, tmalecek, ttakamiy, vkumar, weaton, xdharmai, yguenane
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in aiohttp, an asynchronous HTTP client/server framework. The parser logic allows non-ASCII decimal characters in the HTTP Range header. This could potentially enable a remote attacker to exploit a request smuggling vulnerability, leading to the bypass of security controls or unauthorized information access.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-01-06 00:01:22 UTC

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Versions 3.13.2 and below contain parser logic which allows non-ASCII decimals to be present in the Range header. There is no known impact, but there is the possibility that there's a method to exploit a request smuggling vulnerability. This issue is fixed in version 3.13.3.