djangorestframework 3.18.1
PkgFire would install this release with a warning.·Checked 7 hours ago·Published 7 September 2026
Why
-
warnVulnerability
Django REST framework: Accept header with many large quoted parameters burns ~19s of CPU per request in content negotiation (fixed in 3.18.2)
-
warnVulnerability
Django REST framework: JSONParser applies an attacker-named codec to the request stream (fixed in 3.18.2)
-
warnVulnerability
Django REST framework: TokenProxy.delete() reports success and revokes nothing (fixed in 3.18.2)
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.