ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-53877

CVE-2026-53877 is listed by An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16..

Published Jul 7, 2026 · catalog updated Oct 25, 2026 · the affected product

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-53877. EPSS is 0.53%. Act only if a listed version of the affected product is installed.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium6.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.53%
Remediation
Version ranges on file
Affected products
cpe djangoproject/django

CVE-2026-53877 is listed by An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16..

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe djangoproject/django< 5.2.16
  • cpe djangoproject/django< 6.0.7

How to fix CVE-2026-53877

  • Upgrade

    CVE-2026-53877 lists a fix boundary at 5.2.16. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 5.2.16

  • Advisory

    Open the inventory_high record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-53877. EPSS is 0.53%. Act only if a listed version of the affected product is installed.

Which versions are affected?

Compare what you have installed with < 5.2.16, < 6.0.7. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-805. EPSS 0.53%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Django security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 7, 2026 · Monitored products — high

    Detected

    CVE-2026-53877 is listed by An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16..

  2. Oct 25, 2026 · Monitored products — high

    Updated

    CVE-2026-53877 is listed by An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16..

Sources

  • Monitored products — highVendor advisoryCVE-2026-53877

    An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. over-reads its in-memory buffer when constructed from a bytes object, which can disclose adjacent memory or cause service degradation via a potential segmentation fault when the property is accessed. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Monitored products — highNov 7, 2026