aiohttp 3.14.3
PkgFire would install this release with a warning.·Checked 15 hours ago·Published 23 July 2026
Why
-
warnVulnerability
aiohttp: Multiple instances of excessive or unbounded memory/CPU use (fixed in 3.14.4)
-
warnVulnerability
AIOHTTP: Secure attribute not enforced for shared cookie (fixed in 3.14.4)
-
warnVulnerability
aiohttp server lacks an initial request/header timeout (fixed in 3.14.4)
-
warnVulnerability
AIOHTTP: Connector pool exhaustion via Max-Age overflow (fixed in 3.14.4)
-
warnVulnerability
AIOHTTP: File descriptor exhaustion in multipart requests (fixed in 3.14.4)
-
warnVulnerability
AIOHTTP: Absolute-form request targets can spoof Request.scheme (fixed in 3.14.4)
-
warnVulnerability
AIOHTTP: Pure-Python parser request smuggling (fixed in 3.14.4)
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Not signed
- Build provenance
- Attested
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.