Skip to main content
VulnerabilityPublished

CVE-2026-53877: djangoproject Django · Buffer Access with Incorrect Length Value

Affects djangoproject DjangoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium : upgrade to 6.0.7 or 5.2.16 when convenient.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.0.7, 5.2.16
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Django and django to 6.0.7 or 5.2.16.

Affected software

ProductAffectedFixed in
djangoprojectDjangoAffected
  • >=6.0 <6.0.7
Fixed in
  • 6.0.7
djangoprojectDjangoAffected
  • >=5.2 <5.2.16
Fixed in
  • 5.2.16
PyPIdjangopkg:pypi/djangoOther threatsAffected
  • >=6.0 <6.0.7
  • >=5.2 <5.2.16
Fixed in
  • 6.0.7
  • 5.2.16

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available that fixes this vulnerability in Django versions 6.0.7 and 5.2.16. Users should upgrade to these or later versions to remediate the issue. Since this is not a cloud service, remediation depends on applying the official Django updates. There is no indication that no action is required or that the issue is already mitigated without patching.

Description

An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `django.contrib.gis.gdal.GDALRaster` 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 `vsi_buffer` 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 like to thank Bence Nagy for reporting this issue.

References

Community reviews

Loading reviews…