Django Rest Framework
Approved changes feed: RSS · Atom
cpe:2.3:a:encode:django-rest-framework:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Encode (8524247b-76d1-57ae-bfeb-3565f3aa5c06) |
|---|---|
| Product | Django Rest Framework (54916808-6884-51d6-9a4c-82fdb2f899cc) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-114137 |
vulnerable | 2026-11-03 10:15:53.815886 |
Django REST framework: TokenProxy.delete() reports success and revokes nothing
HIGH (7.4)
Django REST framework is a toolkit for building Web APIs. From 3.12.0 until 3.18.2, TokenProxy.delete() in rest_framework/authtoken/models.py uses the proxy's user-id pk while the concrete Token token-string primary key identifies rows, so Django issues a deletion query that matches no row and reports zero deletions without raising an error. Applications, administrative integrations, or operational scripts that revoke credentials through a TokenProxy instance can therefore believe revocation succeeded while the token remains live and continues authenticating. DRF's own TokenAdmin.delete_model workaround is not affected, but other callers can leave access available indefinitely because DRF tokens do not expire automatically. This issue is fixed in version 3.18.2.
Published: 2026-10-21T20:06:57.790Z
Updated: 2026-10-23T15:08:55.473Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-114136 |
vulnerable | 2026-11-03 10:15:53.741157 |
Django REST framework: JSONParser applies an attacker-named codec to the request stream
HIGH (7.5)
Django REST framework is a toolkit for building Web APIs. From 3.6.4 until 3.18.2, JSONParser.parse in rest_framework/parsers.py uses the client-supplied Content-Type charset value with codecs.getreader, which accepts byte-transform codecs such as bz2_codec rather than only text encodings. A remote unauthenticated client can therefore cause a compressed JSON request body to be expanded after Django has enforced DATA_UPLOAD_MAX_MEMORY_SIZE against only the wire bytes, allowing a very small request to consume substantial per-worker memory. The default parser set is sufficient, and any reachable endpoint that accepts a JSON body is affected. This issue is fixed in version 3.18.2.
Published: 2026-10-21T20:02:41.030Z
Updated: 2026-10-30T19:24:46.203Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-73229 |
vulnerable | 2026-09-16 04:33:09.561987 |
Django REST framework: AdminRenderer may disclose GET-protected data when rendering invalid write requests
MEDIUM (4.3)
Django REST framework is a powerful and flexible toolkit for building Web APIs. Prior to 3.17.2, Django REST Framework's rest_framework/renderers.py AdminRenderer.render() uses override_method() to simulate GET and directly invokes view.get() without view.check_permissions() while rendering an invalid write request, allowing a 400 Bad Request HTML response to disclose data from a GET representation that the requester is not permitted to access. This issue is fixed in version 3.17.2.
Published: 2026-08-11T18:59:34.151Z
Updated: 2026-08-11T20:06:33.042Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.