CVE-2026-71238
Hardcoded SECRET_KEY and DEBUG=True in DjangoCRM enable full account takeover.
Is CVE-2026-71238 being exploited?
Not confirmed. CVE-2026-71238 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-71238?
CVE-2026-71238 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71238?
Not known from our data. No patch reference has been recorded for CVE-2026-71238, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-71238 affect?
CVE-2026-71238 affects DjangoCRM (webcrm/settings.py), Deployments using default SECRET_KEY/DEBUG=True, Public repo clones containing committed secrets. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71238?
Rotate SECRET_KEY and leaked creds; move SECRET_KEY to env, set DEBUG=False, invalidate sessions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Forge session cookies, CSRF and password-reset tokens to achieve full account takeover; DEBUG pages can leak credentials.
Immediate action required