An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango's `django.contrib.gis.geos.GEOSGeometry` is subject to a potential denial-of-service when parsing deeply nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library. Spatial field lookups and the `django.contrib.gis.forms.GeometryField` form field are also affected. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Andrew MacPherson and kimchunbok_ for reporting this issue.

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups
    optimistically parse the right-hand-side value as a raster by passing it to the
    `django.contrib.gis.gdal.GDALRaster` constructor. Any value used in a spatial lookup against a
    `GeometryField` or `RasterField` reaches this constructor, including untrusted input, for example a
    spatial-field filter submitted through the Django admin changelist query string by a staff user with view
    permission. A `dict`, or a `str` holding its JSON representation, is opened in write mode regardless of
    the constructor's `write=False` default, allowing a file with an attacker-chosen name and contents to be
    written through a file-backed GDAL driver. Any other `str` is treated as a datasource, allowing an
    outbound network request through a GDAL virtual filesystem handler. Writing a file to a location later
    imported by the application can result in remote code execution. Earlier, unsupported Django series (such
    as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Bence
    Nagy, localhost-detect, and kimchunbok_ for reporting this issue. (CVE-2026-15307)

  - An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.
    `django.utils.translation.check_for_language()` is subject to a potential denial-of-service attack when
    given many distinct, very long language codes, which are retained as keys in an in-memory cache and
    consume process memory. Such codes reach the function through the `django.views.i18n.set_language()` view,
    which is not routed by default. The consumed memory is bounded, since request data is limited by the
    `DATA_UPLOAD_MAX_MEMORY_SIZE` setting (default 2.5 MB) and the cache holds a fixed maximum number of
    entries. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may
    also be affected. Django would like to thank Jaeyoung Jang for reporting this issue. (CVE-2026-15337)

  - An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango's
    `django.contrib.gis.geos.GEOSGeometry` is subject to a potential denial-of-service when parsing deeply
    nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-
    encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library.
    Spatial field lookups and the `django.contrib.gis.forms.GeometryField` form field are also affected.
    Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be
    affected. Django would like to thank Andrew MacPherson and kimchunbok_ for reporting this issue.
    (CVE-2026-15830)

  - An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.
    `django.contrib.admin.utils.display_for_field()` renders `URLField` values as clickable links in the admin
    without validating the URL. A value stored with an unsafe scheme is displayed as a link on changelist and
    read-only admin pages, which allows cross-site scripting against staff users who click the link.
    Exploitation requires the unsafe value to already be stored in the database. `URLField` validation through
    a `ModelForm` or the admin rejects unsafe schemes, so this affects applications that persist `URLField`
    data without running model validation, for example through direct queryset writes, deserialization, or
    bulk import of untrusted input. Django would like to thank Egor Saltykov for reporting this issue.
    (CVE-2026-15920)

The remote openSUSE 16 host has a package installed that is affected by multiple vulnerabilities as referenced in the openSUSE-SU-2026:21543-1 advisory.

    Changes in python-Django:

    - CVE-2026-15307: server-side file-write and request forgery via spatial lookups (bsc#1272997)
    - CVE-2026-15337: potential denial-of-service vulnerability in `check_for_language()` (bsc#1272998)
    - CVE-2026-15830: potential denial-of-service vulnerability via nested geometry collections (bsc#1272999)
    - CVE-2026-15920: potential cross-site scripting via `URLField` values in the admin (bsc#1273000)

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The detected version of the Django Python package is 5.2.x prior to 5.2.17 or 6.0.x prior to 6.0.8. It is, therefore, affected by multiple vulnerabilities, including:

  - GeoDjango spatial lookups pass untrusted input to the GDALRaster constructor, allowing an attacker to write     arbitrary files via a file-backed GDAL driver or trigger outbound network requests via GDAL virtual filesystem     handlers, potentially resulting in remote code execution. (CVE-2026-15307)

  - django.contrib.admin.utils.display_for_field() renders URLField values as clickable links without validating     the URL scheme, allowing cross-site scripting against staff users who click a link with an unsafe scheme stored     in the database. (CVE-2026-15920)

  - django.utils.translation.check_for_language() retains many distinct, very long language codes as keys in an     in-memory cache, allowing a potential denial-of-service attack that consumes process memory. (CVE-2026-15337)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:3503-1 advisory.

    - CVE-2026-15307: server-side file-write and request forgery via spatial lookups (bsc#1272997).
    - CVE-2026-15337: potential denial-of-service vulnerability in `check_for_language()` (bsc#1272998).
    - CVE-2026-15830: potential denial-of-service vulnerability via nested geometry collections (bsc#1272999).
    - CVE-2026-15920: potential cross-site scripting via `URLField` values in the admin (bsc#1273000).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango's     `django.contrib.gis.geos.GEOSGeometry` is subject to a potential denial-of-service when parsing deeply     nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-     encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library.
    Spatial field lookups and the `django.contrib.gis.forms.GeometryField` form field are also affected.
    Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be     affected. Django would like to thank Andrew MacPherson and kimchunbok_ for reporting this issue.
    (CVE-2026-15830)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
445846	Alpine: multiple py3-django packages: security update to 5.2.17-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	Local	high
445846	Alpine: multiple py3-django packages: security update to 5.2.17-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	Local	high
333512	openSUSE 16 Security Update : python-Django (openSUSE-SU-2026:21543-1)	Nessus	SuSE Local Security Checks	Local	high
333309	Python Library Django 5.2.x < 5.2.17 / 6.0.x < 6.0.8 Multiple Vulnerabilities	Nessus	Misc.	Local	high
333043	SUSE SLES15 Security Update : python-Django (SUSE-SU-2026:3503-1)	Nessus	SuSE Local Security Checks	Local	high
332067	Linux Distros Unpatched Vulnerability : CVE-2026-15830	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-15830

medium

Tenable Plugins

high

high

high

high

high

medium