CVE-2026-53877

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreMEDIUM 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.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8MEDIUMmedium confidence
EG Risk
22
EG Risk 22/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity48% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

Published

July 7, 2026

Last Modified

July 9, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
Patch available.
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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-django2:2.2.24-1 ... 3:6.1~rc1-1 (184 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:3.2.19-1 ... 3:6.1~rc1-1 (110 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:4.2.23-1 ... 3:6.1~rc1-1 (64 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:4.2.23-1 ... 3:5.2~rc1-1 (44 versions)
  • every version up to 3:5.2.16-1: fixed in 3:5.2.16-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
django5.2 ... 6.0.6 (23 versions)
  • every version up to 5.2.16: fixed in 5.2.16
  • 6.0.0 up to 6.0.7: fixed in 6.0.7
  • 5.2 up to 5.2.16: fixed in 5.2.16
  • 6.0 up to 6.0.7: fixed in 6.0.7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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.

Showing the most recent 100 of 146 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-28 13:37 UTCEG score recompute
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-23 06:18 UTCEG score recompute
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 05:50 UTCEG score recompute
  22. 2026-09-17 19:31 UTCEPSS rescore
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-14 09:31 UTCEG score recompute
Show 75 more
  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-13 08:32 UTCEG score recompute
  3. 2026-09-12 03:44 UTCEG score recompute
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-10 09:35 UTCEPSS rescore
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-05 22:54 UTCEG score recompute
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-09-01 04:40 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 07:43 UTCEG score recompute
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 21:55 UTCEG score recompute
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-26 13:00 UTCEG score recompute
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 10:20 UTCEG score recompute
  24. 2026-08-23 06:10 UTCEG score recompute
  25. 2026-08-23 00:19 UTCEPSS rescore
  26. 2026-08-22 05:11 UTCEG score recompute
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-21 04:12 UTCEG score recompute
  29. 2026-08-20 22:55 UTCEPSS rescore
  30. 2026-08-20 02:16 UTCEG score recompute
  31. 2026-08-19 17:04 UTCEPSS rescore
  32. 2026-08-18 20:48 UTCEG score recompute
  33. 2026-08-18 13:48 UTCEPSS rescore
  34. 2026-08-17 13:47 UTCEPSS rescore
  35. 2026-08-17 11:53 UTCEG score recompute
  36. 2026-08-16 14:56 UTCEPSS rescore
  37. 2026-08-16 10:54 UTCEG score recompute
  38. 2026-08-16 02:14 UTCEPSS rescore
  39. 2026-08-15 09:56 UTCEG score recompute
  40. 2026-08-15 01:30 UTCEPSS rescore
  41. 2026-08-14 08:57 UTCEG score recompute
  42. 2026-08-13 22:00 UTCEPSS rescore
  43. 2026-08-13 07:59 UTCEG score recompute
  44. 2026-08-12 13:51 UTCEPSS rescore
  45. 2026-08-12 07:00 UTCEG score recompute
  46. 2026-08-11 06:01 UTCEG score recompute
  47. 2026-08-11 00:00 UTCEPSS rescore
  48. 2026-08-10 05:03 UTCEG score recompute
  49. 2026-08-09 13:46 UTCEPSS rescore
  50. 2026-08-09 04:04 UTCEG score recompute
  51. 2026-08-08 16:37 UTCEPSS rescore
  52. 2026-08-08 03:06 UTCEG score recompute
  53. 2026-08-07 02:07 UTCEG score recompute
  54. 2026-08-07 02:07 UTCGHSA enrichment
  55. 2026-08-06 13:47 UTCEPSS rescore
  56. 2026-08-06 01:08 UTCEG score recompute
  57. 2026-08-06 01:08 UTCGHSA enrichment
  58. 2026-08-05 19:17 UTCEPSS rescore
  59. 2026-08-05 00:09 UTCEG score recompute
  60. 2026-08-05 00:09 UTCGHSA enrichment
  61. 2026-08-04 15:10 UTCEPSS rescore
  62. 2026-08-04 10:39 UTCEPSS rescore
  63. 2026-08-03 23:08 UTCEG score recompute
  64. 2026-08-03 23:08 UTCGHSA enrichment
  65. 2026-08-03 10:36 UTCEPSS rescore
  66. 2026-08-02 22:10 UTCEG score recompute
  67. 2026-08-02 22:10 UTCGHSA enrichment
  68. 2026-08-02 02:27 UTCEPSS rescore
  69. 2026-08-01 21:11 UTCEG score recompute
  70. 2026-08-01 21:11 UTCGHSA enrichment
  71. 2026-08-01 04:16 UTCEPSS rescore
  72. 2026-07-31 20:12 UTCGHSA enrichment
  73. 2026-07-30 19:14 UTCEG score recompute
  74. 2026-07-30 19:14 UTCGHSA enrichment
  75. 2026-07-30 16:28 UTCEPSS rescore

Related CVEs(same product + same CWE)

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 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 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53877?
CVE-2026-53877 has a CVSS base score of 4.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53877?
A fix for CVE-2026-53877 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53877 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs