{
 "version": "https://jsonfeed.org/version/1.1",
 "title": "djangoproject django: all CVE events",
 "home_page_url": "https://patchwire.jonathanross.dev/products/djangoproject--django/",
 "feed_url": "https://patchwire.jonathanross.dev/feeds/products/djangoproject--django/all.json",
 "authors": [
  {
   "name": "Patchwire"
  }
 ],
 "language": "en",
 "items": [
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-87975/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-87975/",
   "title": "CVE-2026-87975 disclosed",
   "content_text": "An issue was discovered in Django 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18.\n`django.forms.models.BaseModelFormSet.save_existing_objects()` used the presence of a primary key on a submitted form's instance as evidence that the instance belonged to the formset's limiting queryset. An object outside that queryset is represented by a newly constructed instance whose primary key can still be populated from submitted data when the model's primary key is a field accepted by the form, such as a `OneToOneField` or parent link used as the primary key of an inline formset's model, or a natural or UUID primary key included in the form's fields. This allows an authenticated user permitted to submit such a formset to delete rows outside the limiting queryset, without any permission on the targeted object, via forged management-form data marking an out-of-queryset object for deletion. Models using the default AutoField primary key are not affected.\nEarlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected.\nDjango would like to thank Seonggwon Yoon for reporting this issue.",
   "date_published": "2026-10-06T13:35:59Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-87975/fixed/debian-12",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-87975/",
   "title": "CVE-2026-87975 fixed in Debian 12",
   "content_text": "Fixed versions: python-django 3:3.2.25-0+deb12u6.",
   "date_published": "2026-10-06T13:35:59Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-87975/fixed/opensuse-tumbleweed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-87975/",
   "title": "CVE-2026-87975 fixed in openSUSE Tumbleweed",
   "content_text": "Fixed versions: python-Django 6.1.2-1.1, python-Django4 4.2.30-6.1, python-Django5 5.2.18-1.1.",
   "date_published": "2026-10-06T13:35:59Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-87975/fixed/suse-linux-enterprise-module-for-package-hub-15-sp7",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-87975/",
   "title": "CVE-2026-87975 fixed in SUSE Linux Enterprise Module for Package Hub 15 SP7",
   "content_text": "Fixed versions: python-Django 4.2.11-150600.3.68.1.",
   "date_published": "2026-10-06T13:35:59Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-87890/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-87890/",
   "title": "CVE-2026-87890 disclosed",
   "content_text": "An issue was discovered in Django 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18.\nAn incomplete fix for CVE-2026-15307 in Django spatial lookups allows an attacker who can supply `bytes` values to cause the Django process to make network requests via a crafted VRT document referencing an external raster source.\nEarlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected.\nDjango would like to thank sicksec for reporting this issue.",
   "date_published": "2026-10-06T13:35:37Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-87890/fixed/opensuse-tumbleweed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-87890/",
   "title": "CVE-2026-87890 fixed in openSUSE Tumbleweed",
   "content_text": "Fixed versions: python-Django 6.1.2-1.1, python-Django4 4.2.30-6.1, python-Django5 5.2.18-1.1.",
   "date_published": "2026-10-06T13:35:37Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-87890/fixed/suse-linux-enterprise-module-for-package-hub-15-sp7",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-87890/",
   "title": "CVE-2026-87890 fixed in SUSE Linux Enterprise Module for Package Hub 15 SP7",
   "content_text": "Fixed versions: python-Django 4.2.11-150600.3.68.1.",
   "date_published": "2026-10-06T13:35:37Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-84429/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-84429/",
   "title": "CVE-2026-84429 disclosed",
   "content_text": "An issue was discovered in Django 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18.\n`django.utils.http.parse_header_parameters()` was subject to a potential denial-of-service attack due to quadratic time complexity when parsing a value with many separators inside a quoted parameter. An unauthenticated request could reach this parsing through headers such as `Accept` or `Content-Type`, for instance via the content negotiation performed by `HttpRequest.accepts()`. The per-call length limit does not bound the combined size of repeated headers.\nEarlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected.\nDjango would like to thank Jisung Chae for reporting this issue.",
   "date_published": "2026-10-06T13:35:17Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-84429/fixed/opensuse-tumbleweed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-84429/",
   "title": "CVE-2026-84429 fixed in openSUSE Tumbleweed",
   "content_text": "Fixed versions: python-Django 6.1.2-1.1, python-Django4 4.2.30-6.1, python-Django5 5.2.18-1.1.",
   "date_published": "2026-10-06T13:35:17Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-84429/fixed/suse-linux-enterprise-module-for-package-hub-15-sp7",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-84429/",
   "title": "CVE-2026-84429 fixed in SUSE Linux Enterprise Module for Package Hub 15 SP7",
   "content_text": "Fixed versions: python-Django 4.2.11-150600.3.68.1.",
   "date_published": "2026-10-06T13:35:17Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-77050/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-77050/",
   "title": "CVE-2026-77050 disclosed",
   "content_text": "An issue was discovered in Django 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18.\n`django.utils.translation.get_supported_language_variant()` is subject to\r\na potential denial-of-service attack when processing many distinct, very long\r\nlanguage codes, which are retained as keys in an in-memory cache and\r\nconsume process memory.\nEarlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected.\nDjango would like to thank Gleb Lizunov for reporting this issue.",
   "date_published": "2026-10-06T13:34:40Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-77050/fixed/debian-12",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-77050/",
   "title": "CVE-2026-77050 fixed in Debian 12",
   "content_text": "Fixed versions: python-django 3:3.2.25-0+deb12u6.",
   "date_published": "2026-10-06T13:34:40Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-77050/fixed/opensuse-tumbleweed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-77050/",
   "title": "CVE-2026-77050 fixed in openSUSE Tumbleweed",
   "content_text": "Fixed versions: python-Django 6.1.2-1.1, python-Django4 4.2.30-6.1, python-Django5 5.2.18-1.1.",
   "date_published": "2026-10-06T13:34:40Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-77050/fixed/suse-linux-enterprise-module-for-package-hub-15-sp7",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-77050/",
   "title": "CVE-2026-77050 fixed in SUSE Linux Enterprise Module for Package Hub 15 SP7",
   "content_text": "Fixed versions: python-Django 4.2.11-150600.3.68.1.",
   "date_published": "2026-10-06T13:34:40Z"
  }
 ]
}