<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 06:44:00 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-351980</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-351980</link>
      <description>EUVD-2026-351980</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-351980</guid>
    </item>
    <item>
      <title>fkie_cve-2026-73228</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-73228</link>
      <description>&lt;p&gt;Django REST framework is a toolkit for building Web APIs. Prior to 3.17.2, Django REST Framework&amp;#39;s request.data parsing in rest_framework/request.py Request._parse() passes the underlying HttpRequest stream to JSONParser and FormParser for application/json and application/x-www-form-urlencoded bodies, bypassing Django&amp;#39;s DATA_UPLOAD_MAX_MEMORY_SIZE protection and allowing oversized request bodies to consume additional memory and CPU. This issue is fixed in version 3.17.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Django REST framework is a toolkit for building Web APIs. Prior to 3.17.2, Django REST Framework&amp;#39;s request.data parsing in rest_framework/request.py Request._parse() passes the underlying HttpRequest stream to JSONParser and FormParser for application/json and application/x-www-form-urlencoded bodies, bypassing Django&amp;#39;s DATA_UPLOAD_MAX_MEMORY_SIZE protection and allowing oversized request bodies to consume additional memory and CPU. This issue is fixed in version 3.17.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-73228</guid>
    </item>
    <item>
      <title>GHSA-2m8g-3cmr-wg3w — Django REST framework: Potential bypass of Django `DATA_UPLOAD_MAX_MEMORY_SIZE` when parsing oversized JSON and urlenco…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2m8g-3cmr-wg3w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: djangorestframework&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;While investigating Django REST Framework&amp;#39;s request parsing behavior, I identified that DRF&amp;#39;s high-level `request.data` parsing appears to bypass Django&amp;#39;s configured `DATA_UPLOAD_MAX_MEMORY_SIZE` protection for `application/json` and `application/x-www-form-urlencoded` request bodies.&lt;/p&gt;
&lt;p&gt;In the tested configurations, Django correctly raises `RequestDataTooBig` when applications access `request.body` or Django&amp;#39;s native `request.POST`, but DRF successfully parses the same oversized payloads through `request.data`.&lt;/p&gt;
&lt;p&gt;This behavior appears to occur because DRF passes the underlying `HttpRequest` object directly to parsers, which consume the request stream through Django&amp;#39;s lower-level streaming interface rather than the guarded `request.body` path.&lt;/p&gt;
&lt;p&gt;I am reporting this privately because I am unsure whether this behavior is considered part of DRF&amp;#39;s intended security boundary, but it appears to bypass a documented Django request-size protection for common DRF request parsing paths and may have availability implications.&lt;/p&gt;
&lt;p&gt;# What I Verified&lt;/p&gt;
&lt;p&gt;I verified the behavior locally using the following combinations:&lt;/p&gt;
&lt;p&gt;* Django **6.0.7** + DRF **3.17.1** → **Affected**
* Django **6.0.7** + DRF **current upstream main** → **Affected**&lt;/p&gt;
&lt;p&gt;For both versions, the observed behavior was:&lt;/p&gt;
&lt;p&gt;```
Django request.body
→ RequestDataTooBig&lt;/p&gt;
&lt;p&gt;Django request.POST (application/x-www-form-urlencoded)
→ RequestDataTooBig&lt;/p&gt;
&lt;p&gt;Django request.read()
→ Reads the entire oversized request body&lt;/p&gt;
&lt;p&gt;DRF request.data
→ Su…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: djangorestframework&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;While investigating Django REST Framework&amp;#39;s request parsing behavior, I identified that DRF&amp;#39;s high-level `request.data` parsing appears to bypass Django&amp;#39;s configured `DATA_UPLOAD_MAX_MEMORY_SIZE` protection for `application/json` and `application/x-www-form-urlencoded` request bodies.&lt;/p&gt;
&lt;p&gt;In the tested configurations, Django correctly raises `RequestDataTooBig` when applications access `request.body` or Django&amp;#39;s native `request.POST`, but DRF successfully parses the same oversized payloads through `request.data`.&lt;/p&gt;
&lt;p&gt;This behavior appears to occur because DRF passes the underlying `HttpRequest` object directly to parsers, which consume the request stream through Django&amp;#39;s lower-level streaming interface rather than the guarded `request.body` path.&lt;/p&gt;
&lt;p&gt;I am reporting this privately because I am unsure whether this behavior is considered part of DRF&amp;#39;s intended security boundary, but it appears to bypass a documented Django request-size protection for common DRF request parsing paths and may have availability implications.&lt;/p&gt;
&lt;p&gt;# What I Verified&lt;/p&gt;
&lt;p&gt;I verified the behavior locally using the following combinations:&lt;/p&gt;
&lt;p&gt;* Django **6.0.7** + DRF **3.17.1** → **Affected**
* Django **6.0.7** + DRF **current upstream main** → **Affected**&lt;/p&gt;
&lt;p&gt;For both versions, the observed behavior was:&lt;/p&gt;
&lt;p&gt;```
Django request.body
→ RequestDataTooBig&lt;/p&gt;
&lt;p&gt;Django request.POST (application/x-www-form-urlencoded)
→ RequestDataTooBig&lt;/p&gt;
&lt;p&gt;Django request.read()
→ Reads the entire oversized request body&lt;/p&gt;
&lt;p&gt;DRF request.data
→ Su…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2m8g-3cmr-wg3w</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11625-1 — python313-djangorestframework-3.18.0-2.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11625-1</link>
      <description>&lt;p&gt;python313-djangorestframework-3.18.0-2.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;python313-djangorestframework-3.18.0-2.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11625-1</guid>
    </item>
    <item>
      <title>PYSEC-2026-3827 — Django REST framework: Potential bypass of Django `DATA_UPLOAD_MAX_MEMORY_SIZE` when parsing oversized JSON and urlenco…</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-3827</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: djangorestframework&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;While investigating Django REST Framework&amp;#39;s request parsing behavior, I identified that DRF&amp;#39;s high-level `request.data` parsing appears to bypass Django&amp;#39;s configured `DATA_UPLOAD_MAX_MEMORY_SIZE` protection for `application/json` and `application/x-www-form-urlencoded` request bodies.&lt;/p&gt;
&lt;p&gt;In the tested configurations, Django correctly raises `RequestDataTooBig` when applications access `request.body` or Django&amp;#39;s native `request.POST`, but DRF successfully parses the same oversized payloads through `request.data`.&lt;/p&gt;
&lt;p&gt;This behavior appears to occur because DRF passes the underlying `HttpRequest` object directly to parsers, which consume the request stream through Django&amp;#39;s lower-level streaming interface rather than the guarded `request.body` path.&lt;/p&gt;
&lt;p&gt;I am reporting this privately because I am unsure whether this behavior is considered part of DRF&amp;#39;s intended security boundary, but it appears to bypass a documented Django request-size protection for common DRF request parsing paths and may have availability implications.&lt;/p&gt;
&lt;p&gt;# What I Verified&lt;/p&gt;
&lt;p&gt;I verified the behavior locally using the following combinations:&lt;/p&gt;
&lt;p&gt;* Django **6.0.7** + DRF **3.17.1** → **Affected**
* Django **6.0.7** + DRF **current upstream main** → **Affected**&lt;/p&gt;
&lt;p&gt;For both versions, the observed behavior was:&lt;/p&gt;
&lt;p&gt;```
Django request.body
→ RequestDataTooBig&lt;/p&gt;
&lt;p&gt;Django request.POST (application/x-www-form-urlencoded)
→ RequestDataTooBig&lt;/p&gt;
&lt;p&gt;Django request.read()
→ Reads the entire oversized request body&lt;/p&gt;
&lt;p&gt;DRF request.data
→ Su…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: djangorestframework&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;While investigating Django REST Framework&amp;#39;s request parsing behavior, I identified that DRF&amp;#39;s high-level `request.data` parsing appears to bypass Django&amp;#39;s configured `DATA_UPLOAD_MAX_MEMORY_SIZE` protection for `application/json` and `application/x-www-form-urlencoded` request bodies.&lt;/p&gt;
&lt;p&gt;In the tested configurations, Django correctly raises `RequestDataTooBig` when applications access `request.body` or Django&amp;#39;s native `request.POST`, but DRF successfully parses the same oversized payloads through `request.data`.&lt;/p&gt;
&lt;p&gt;This behavior appears to occur because DRF passes the underlying `HttpRequest` object directly to parsers, which consume the request stream through Django&amp;#39;s lower-level streaming interface rather than the guarded `request.body` path.&lt;/p&gt;
&lt;p&gt;I am reporting this privately because I am unsure whether this behavior is considered part of DRF&amp;#39;s intended security boundary, but it appears to bypass a documented Django request-size protection for common DRF request parsing paths and may have availability implications.&lt;/p&gt;
&lt;p&gt;# What I Verified&lt;/p&gt;
&lt;p&gt;I verified the behavior locally using the following combinations:&lt;/p&gt;
&lt;p&gt;* Django **6.0.7** + DRF **3.17.1** → **Affected**
* Django **6.0.7** + DRF **current upstream main** → **Affected**&lt;/p&gt;
&lt;p&gt;For both versions, the observed behavior was:&lt;/p&gt;
&lt;p&gt;```
Django request.body
→ RequestDataTooBig&lt;/p&gt;
&lt;p&gt;Django request.POST (application/x-www-form-urlencoded)
→ RequestDataTooBig&lt;/p&gt;
&lt;p&gt;Django request.read()
→ Reads the entire oversized request body&lt;/p&gt;
&lt;p&gt;DRF request.data
→ Su…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-3827</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-73228</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-73228</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: djangorestframework, Ubuntu:18.04:LTS: djangorestframework, Ubuntu:20.04:LTS: djangorestframework, Ubuntu:22.04:LTS: djangorestframework, Ubuntu:24.04:LTS: djangorestframework, Ubuntu:26.04:LTS: djangorestframework&lt;/p&gt;
&lt;p&gt;Django REST framework is a toolkit for building Web APIs. Prior to 3.17.2, Django REST Framework&amp;#39;s request.data parsing in rest_framework/request.py Request._parse() passes the underlying HttpRequest stream to JSONParser and FormParser for application/json and application/x-www-form-urlencoded bodies, bypassing Django&amp;#39;s DATA_UPLOAD_MAX_MEMORY_SIZE protection and allowing oversized request bodies to consume additional memory and CPU. This issue is fixed in version 3.17.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: djangorestframework, Ubuntu:18.04:LTS: djangorestframework, Ubuntu:20.04:LTS: djangorestframework, Ubuntu:22.04:LTS: djangorestframework, Ubuntu:24.04:LTS: djangorestframework, Ubuntu:26.04:LTS: djangorestframework&lt;/p&gt;
&lt;p&gt;Django REST framework is a toolkit for building Web APIs. Prior to 3.17.2, Django REST Framework&amp;#39;s request.data parsing in rest_framework/request.py Request._parse() passes the underlying HttpRequest stream to JSONParser and FormParser for application/json and application/x-www-form-urlencoded bodies, bypassing Django&amp;#39;s DATA_UPLOAD_MAX_MEMORY_SIZE protection and allowing oversized request bodies to consume additional memory and CPU. This issue is fixed in version 3.17.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-73228</guid>
    </item>
  </channel>
</rss>
