Potential sensitive information disclosed in error reports
CVE-2021-21416GHSA-58c7-px5v-82hh
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (django-registration 3.1.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI django-registration
- Affected
- < 3.1.2
- Fixed in
- 3.1.2
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-58c7-px5v-82hh lists affected ranges: PyPI django-registration >=0 <3.1.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-58c7-px5v-82hh lists affected ranges: PyPI django-registration >=0 <3.1.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 2.0 · CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source
- EPSS
- CVE-2021-21416: 0.41% estimated exploitation activity in the next 30 days; percentile 35.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
django-registration is a user-registration application for Django. Impact The django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django. Triggering this requires the following conditions: A site is using django-registration < 3.1.2 The site has detailed error reports (such as Django's emailed error reports to site staff/developers) enabled A server-side error (HTTP 5xx) occurs during an attempt by a user to register an account Under these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password). Patches As of version 3.1.2, django-registration properly…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-58c7-px5v-82hh
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-58c7-px5v-82hh
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2021-21416 Advisory: Potential sensitive information disclosed in error reports IDs: CVE-2021-21416, GHSA-58c7-px5v-82hh Record: https://patchnext.com/advisories/cve-2021-21416 (revision 3, source checked 26 Oct 2026, 13:17 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 2.0) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: django-registration 3.1.2. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI django-registration: affected < 3.1.2; fixed in 3.1.2 ## Suggested inspection (read-only) - `python -m pip show django-registration`: 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 django-registration. - 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://osv.dev/vulnerability/GHSA-58c7-px5v-82hh (OSV record GHSA-58c7-px5v-82hh lists affected ranges: PyPI django-registration >=0 <3.1.2 (fixed)) - Verified: https://github.com/advisories/GHSA-58c7-px5v-82hh (GitHub-reviewed advisory GHSA-58c7-px5v-82hh lists affected ranges: PyPI django-registration >=0 <3.1.2) Commands are suggestions: review each one before running it.
Loading voting…