---
id: CVE-2026-53877
aliases:
  - GHSA-crhf-3pfg-w68w
  - BIT-django-2026-53877
  - PYSEC-2026-2091
title: ' Django: GDALRaster may over-read heap memory when constructed from bytes'
summary: ' Django: GDALRaster may over-read heap memory when constructed from bytes'
severity: medium
cvss: 4.8
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L'
vendor: django
product: django
ecosystem: pip
affected:
  - django < 5.2.16
  - 'django >= 6.0.0, < 6.0.7'
patched:
  - django 5.2.16
  - django 6.0.7
published: '2026-07-07'
updated: '2026-09-10'
sourceUpdated: '2026-09-10T03:51:11.475072075Z'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/GHSA-crhf-3pfg-w68w'
references:
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-53877'
  - url: >-
      https://github.com/django/django/commit/38dfbd27d7d4f4e6eaa087d7a90f2613fbf55b3a
  - url: >-
      https://github.com/django/django/commit/6c66eb8cec52b303af85c2c6e4dd00aa37654dbc
  - url: >-
      https://github.com/django/django/commit/6ca2bbe2efce21010eff48f1f36a3f621d698ed8
  - url: 'https://docs.djangoproject.com/en/dev/releases/security'
  - url: >-
      https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2026-2091.yaml
  - url: 'https://groups.google.com/g/django-announce'
  - url: 'https://www.djangoproject.com/weblog/2026/jul/07/security-releases'
  - url: 'https://docs.djangoproject.com/en/dev/releases/security/'
  - url: 'https://www.djangoproject.com/weblog/2026/jul/07/security-releases/'
tags:
  - osv
  - pip
epss: 0.00437
epssPercentile: 0.37463
ingestedAt: '2026-07-10T18:56:50.632Z'
---

## Overview

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.

## Affected packages

- `django < 5.2.16`
- `django >= 6.0.0, < 6.0.7`

## Remediation

Upgrade to a patched release:

- `django 5.2.16`
- `django 6.0.7`