CVE-2026-53877

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreHIGH confidence

Score 4.8 from GitHub Security Advisory published 2026-07-07. a secondary CVSS source baseline 4.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
4.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.8
EG Score
4.8(high)
EG Risk
—
EPSS
21.3%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 9, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
No patch confirmed yet.
generic

Django security releases issued: 6.0.7 and 5.2.16 | Weblog | Django

https://www.djangoproject.com/weblog/2026/jul/07/security-releases/
generic
https://groups.google.com/g/django-announce
generic

Archive of security issues | Django documentation | Django

https://docs.djangoproject.com/en/dev/releases/security/

Vendor Advisories for CVE-2026-53877(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
django5.2 ... 6.0.6 (23 versions)6.0.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-20 17:08 UTCEPSS rescore
  3. 2026-07-19 14:31 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 23:43 UTCGHSA enrichment
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 22:45 UTCGHSA enrichment
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-14 21:46 UTCGHSA enrichment
  15. 2026-07-13 22:31 UTCEPSS rescore
  16. 2026-07-13 20:47 UTCGHSA enrichment
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-12 19:48 UTCGHSA enrichment
  20. 2026-07-12 05:46 UTCEPSS rescore
  21. 2026-07-11 18:49 UTCGHSA enrichment
  22. 2026-07-11 08:27 UTCEPSS rescore
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-10 17:50 UTCGHSA enrichment
  25. 2026-07-09 19:10 UTCEPSS rescore
Show 7 more
  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-09 16:51 UTCGHSA enrichment
  3. 2026-07-08 15:51 UTCGHSA enrichment
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-08 15:16 UTCEPSS rescore
  6. 2026-07-07 14:52 UTCEG score recompute
  7. 2026-07-07 14:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53877?
CVE-2026-53877 is a medium vulnerability published on July 7, 2026. 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…
When was CVE-2026-53877 disclosed?
CVE-2026-53877 was first published in the National Vulnerability Database on July 7, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53877 actively exploited?
CVE-2026-53877 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53877?
CVE-2026-53877 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-53877?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53877, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53877

Explore →

Is Your Infrastructure Affected by CVE-2026-53877?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs