Cloudanix VulnDB

CVE-2026-73229

Medium · 4.3

CVSS

4.3

EPSS

0.4%

Published

Aug 11, 2026

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A web API toolkit could accidentally show some users information they are not allowed to see when they trigger certain error messages.

Exploitation
Remote Authenticated
Attacker needs
Low Privilege
Complexity
Low
Impact
Data Exposure
Component
Web Framework
Class
Information Disclosure
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

The AdminRenderer.render() method in rest_framework/renderers.py invokes view.get() via override_method() to simulate a GET during invalid write request rendering without first calling view.check_permissions(), causing a 400 Bad Request response to include serialized data from a privileged GET representation.

Why it matters to the business

Organizations using the affected Django REST Framework version risk limited unauthorized disclosure of sensitive API data to authenticated but unprivileged users during normal error responses, potentially violating data access policies and requiring urgent patching to maintain compliance.

How an attack unfolds

An authenticated attacker submits an invalid write request (such as a malformed POST or PUT) to an endpoint they lack write permissions for; the AdminRenderer then renders the resulting 400 error by directly calling the view's GET handler without permission checks, returning HTML that leaks data the attacker could not otherwise access.

How to fix it

Upgrade Django REST Framework to version 3.17.2 or later; after upgrade, verify that AdminRenderer no longer bypasses permission checks on error paths and re-test affected endpoints with invalid write requests.

How to confirm the fix worked

Confirm the installed package version is at least 3.17.2, then replay an invalid write request against a permission-protected endpoint while logged in as an unprivileged user and verify the 400 response no longer contains GET-representation data.

Typical attack path

  1. Authenticate with low-privileged credentials
  2. Craft and send an invalid write request to a protected resource
  3. Receive 400 Bad Request HTML response containing unauthorized GET data
  4. Parse leaked data from the error page

How to detect it

Search web server and application logs for 400 responses generated by AdminRenderer on write endpoints; inspect response bodies for serialized objects that would normally be restricted by permission checks.

What your security team should do

  • Immediately upgrade all Django REST Framework installations to 3.17.2
  • Audit API endpoints that use the AdminRenderer for any custom permission logic
  • Add monitoring for 400 responses on write endpoints that return unusually large or data-rich HTML bodies
  • Review access logs for repeated invalid write attempts from authenticated users

The record

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.

Affected packages

Ecosystem Package Introduced Fixed

Related vulnerabilities