Django REST Framework (< 3.18.2) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/django-rest-framework--3.18.2/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 21 Oct 2026 21:41:30 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgDjango REST framework: Denial of Service via Accept header parsing (CVE-2026-114138)https://feed.craftedsignal.io/briefs/2026-10-django-rest-framework-dos/Wed, 21 Oct 2026 21:41:30 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-django-rest-framework-dos/Django REST framework versions prior to 3.18.2 are susceptible to a Denial of Service attack where specially crafted Accept headers cause CPU-intensive parsing and thread exhaustion.Django REST framework versions prior to 3.18.2 contain a vulnerability in the DefaultContentNegotiation class, specifically within get_accept_list and select_renderer. The framework fails to limit the number and aggregate size of media type tokens in the HTTP Accept header. An attacker can supply a large number of distinct media types containing complex, quoted parameters and excessive semicolons. This forces the server's parser into a cycle of intensive operations that pin synchronous worker threads, leading to service unavailability.

Impact

A remote, unauthenticated attacker can cause a Denial of Service by exhausting synchronous worker threads, rendering the API unresponsive until the malicious requests cease.

Recommendation

  • Upgrade Django REST framework to version 3.18.2 or later to include the patch for CVE-2026-114138.
  • Implement request-level limits on the size and complexity of HTTP headers at the web server or reverse proxy layer (e.g., nginx, Apache) to mitigate the impact of abnormally large Accept headers before they reach the application tier.
]]>lowadvisory