Django REST framework: AdminRenderer may disclose GET-protected data when rendering invalid write requests

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-73229: 0.37% estimated exploitation activity in the next 30 days; percentile 31.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary AdminRenderer may disclose data that would normally be protected by GET permissions when rendering a 400 Bad Request response for an invalid write request. If a view allows POST (or another write method) but denies GET, an invalid request rendered through AdminRenderer can invoke the view's GET handler and include data from the GET representation in the generated HTML response. This behavior appears to be specific to AdminRenderer and does not affect the normal JSON rendering path. --- Details While investigating the AdminRenderer rendering flow, I observed that invalid write requests are rendered by temporarily overriding the request method and invoking the view's GET handler: This execution path differs from a normal GET request. Under normal request processing, a GET request flows through: However, during AdminRenderer rendering, the renderer directly invokes: view.get(...) A view whose permission class explicitly allowed POST but denied GET still executed its GET handler…

Published by the source

1 Sep 2026, 19:24 UTC

Last modified by the source

1 Sep 2026, 19:24 UTC

Source last checked

26 Oct 2026, 13:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g47c-3xmw-q6m2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73229

Advisory: Django REST framework: AdminRenderer may disclose GET-protected data when rendering invalid write requests
IDs: CVE-2026-73229, GHSA-g47c-3xmw-q6m2
Record: https://patchnext.com/advisories/cve-2026-73229 (revision 1, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: djangorestframework 3.17.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI djangorestframework: affected <= 3.17.1; fixed in 3.17.2

## Suggested inspection (read-only)
- `python -m pip show djangorestframework`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on djangorestframework.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g47c-3xmw-q6m2 (GitHub-reviewed advisory GHSA-g47c-3xmw-q6m2 lists affected ranges: PyPI djangorestframework >=0 <=3.17.1)

Commands are suggestions: review each one before running it.