<?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 18:42:04 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-351259</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-351259</link>
      <description>EUVD-2026-351259</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-351259</guid>
    </item>
    <item>
      <title>fkie_cve-2026-73229</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-73229</link>
      <description>&lt;p&gt;Django REST framework is a powerful and flexible toolkit for building Web APIs. Prior to 3.17.2, Django REST Framework&amp;#39;s rest_framework/renderers.py AdminRenderer.render() uses override_method() to simulate GET and directly invokes view.get() without view.check_permissions() while rendering an invalid write request, allowing a 400 Bad Request HTML response to disclose data from a GET representation that the requester is not permitted to access. This issue is fixed in version 3.17.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Django REST framework is a powerful and flexible toolkit for building Web APIs. Prior to 3.17.2, Django REST Framework&amp;#39;s rest_framework/renderers.py AdminRenderer.render() uses override_method() to simulate GET and directly invokes view.get() without view.check_permissions() while rendering an invalid write request, allowing a 400 Bad Request HTML response to disclose data from a GET representation that the requester is not permitted to access. 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-73229</guid>
    </item>
    <item>
      <title>GHSA-g47c-3xmw-q6m2 — Django REST framework: AdminRenderer may disclose GET-protected data when rendering invalid write requests</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g47c-3xmw-q6m2</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;AdminRenderer may disclose data that would normally be protected by GET permissions when rendering a 400 Bad Request response for an invalid write request.&lt;/p&gt;
&lt;p&gt;If a view allows POST (or another write method) but denies GET, an invalid request rendered through AdminRenderer can invoke the view&amp;#39;s GET handler and include data from the GET representation in the generated HTML response.&lt;/p&gt;
&lt;p&gt;This behavior appears to be specific to AdminRenderer and does not affect the normal JSON rendering path.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;Details&lt;/p&gt;
&lt;p&gt;While investigating the AdminRenderer rendering flow, I observed that invalid write requests are rendered by temporarily overriding the request method and invoking the view&amp;#39;s GET handler:&lt;/p&gt;
&lt;p&gt;```
with override_method(view, request, &amp;#34;GET&amp;#34;) as request:
    response = view.get(request, *view.args, **view.kwargs)&lt;/p&gt;
&lt;p&gt;data = response.data
```&lt;/p&gt;
&lt;p&gt;This execution path differs from a normal GET request.&lt;/p&gt;
&lt;p&gt;Under normal request processing, a GET request flows through:&lt;/p&gt;
&lt;p&gt;```
APIView.dispatch()
    └── APIView.initial()
            └── APIView.check_permissions()
```&lt;/p&gt;
&lt;p&gt;However, during AdminRenderer rendering, the renderer directly invokes:&lt;/p&gt;
&lt;p&gt;view.get(...)&lt;/p&gt;
&lt;p&gt;A view whose permission class explicitly allowed POST but denied GET still executed its GET handler while rendering an invalid POST request through AdminRenderer.&lt;/p&gt;
&lt;p&gt;As a result, data intended to be available only through an authorized GET request was included in the generated HTML response.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;Proof of Concept&lt;/p&gt;
&lt;p&gt;Using a standard ListCreateAP…&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;AdminRenderer may disclose data that would normally be protected by GET permissions when rendering a 400 Bad Request response for an invalid write request.&lt;/p&gt;
&lt;p&gt;If a view allows POST (or another write method) but denies GET, an invalid request rendered through AdminRenderer can invoke the view&amp;#39;s GET handler and include data from the GET representation in the generated HTML response.&lt;/p&gt;
&lt;p&gt;This behavior appears to be specific to AdminRenderer and does not affect the normal JSON rendering path.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;Details&lt;/p&gt;
&lt;p&gt;While investigating the AdminRenderer rendering flow, I observed that invalid write requests are rendered by temporarily overriding the request method and invoking the view&amp;#39;s GET handler:&lt;/p&gt;
&lt;p&gt;```
with override_method(view, request, &amp;#34;GET&amp;#34;) as request:
    response = view.get(request, *view.args, **view.kwargs)&lt;/p&gt;
&lt;p&gt;data = response.data
```&lt;/p&gt;
&lt;p&gt;This execution path differs from a normal GET request.&lt;/p&gt;
&lt;p&gt;Under normal request processing, a GET request flows through:&lt;/p&gt;
&lt;p&gt;```
APIView.dispatch()
    └── APIView.initial()
            └── APIView.check_permissions()
```&lt;/p&gt;
&lt;p&gt;However, during AdminRenderer rendering, the renderer directly invokes:&lt;/p&gt;
&lt;p&gt;view.get(...)&lt;/p&gt;
&lt;p&gt;A view whose permission class explicitly allowed POST but denied GET still executed its GET handler while rendering an invalid POST request through AdminRenderer.&lt;/p&gt;
&lt;p&gt;As a result, data intended to be available only through an authorized GET request was included in the generated HTML response.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;Proof of Concept&lt;/p&gt;
&lt;p&gt;Using a standard ListCreateAP…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g47c-3xmw-q6m2</guid>
    </item>
    <item>
      <title>PYSEC-2026-3828 — Django REST framework: AdminRenderer may disclose GET-protected data when rendering invalid write requests</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-3828</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;AdminRenderer may disclose data that would normally be protected by GET permissions when rendering a 400 Bad Request response for an invalid write request.&lt;/p&gt;
&lt;p&gt;If a view allows POST (or another write method) but denies GET, an invalid request rendered through AdminRenderer can invoke the view&amp;#39;s GET handler and include data from the GET representation in the generated HTML response.&lt;/p&gt;
&lt;p&gt;This behavior appears to be specific to AdminRenderer and does not affect the normal JSON rendering path.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;Details&lt;/p&gt;
&lt;p&gt;While investigating the AdminRenderer rendering flow, I observed that invalid write requests are rendered by temporarily overriding the request method and invoking the view&amp;#39;s GET handler:&lt;/p&gt;
&lt;p&gt;```
with override_method(view, request, &amp;#34;GET&amp;#34;) as request:
    response = view.get(request, *view.args, **view.kwargs)&lt;/p&gt;
&lt;p&gt;data = response.data
```&lt;/p&gt;
&lt;p&gt;This execution path differs from a normal GET request.&lt;/p&gt;
&lt;p&gt;Under normal request processing, a GET request flows through:&lt;/p&gt;
&lt;p&gt;```
APIView.dispatch()
    └── APIView.initial()
            └── APIView.check_permissions()
```&lt;/p&gt;
&lt;p&gt;However, during AdminRenderer rendering, the renderer directly invokes:&lt;/p&gt;
&lt;p&gt;view.get(...)&lt;/p&gt;
&lt;p&gt;A view whose permission class explicitly allowed POST but denied GET still executed its GET handler while rendering an invalid POST request through AdminRenderer.&lt;/p&gt;
&lt;p&gt;As a result, data intended to be available only through an authorized GET request was included in the generated HTML response.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;Proof of Concept&lt;/p&gt;
&lt;p&gt;Using a standard ListCreateAP…&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;AdminRenderer may disclose data that would normally be protected by GET permissions when rendering a 400 Bad Request response for an invalid write request.&lt;/p&gt;
&lt;p&gt;If a view allows POST (or another write method) but denies GET, an invalid request rendered through AdminRenderer can invoke the view&amp;#39;s GET handler and include data from the GET representation in the generated HTML response.&lt;/p&gt;
&lt;p&gt;This behavior appears to be specific to AdminRenderer and does not affect the normal JSON rendering path.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;Details&lt;/p&gt;
&lt;p&gt;While investigating the AdminRenderer rendering flow, I observed that invalid write requests are rendered by temporarily overriding the request method and invoking the view&amp;#39;s GET handler:&lt;/p&gt;
&lt;p&gt;```
with override_method(view, request, &amp;#34;GET&amp;#34;) as request:
    response = view.get(request, *view.args, **view.kwargs)&lt;/p&gt;
&lt;p&gt;data = response.data
```&lt;/p&gt;
&lt;p&gt;This execution path differs from a normal GET request.&lt;/p&gt;
&lt;p&gt;Under normal request processing, a GET request flows through:&lt;/p&gt;
&lt;p&gt;```
APIView.dispatch()
    └── APIView.initial()
            └── APIView.check_permissions()
```&lt;/p&gt;
&lt;p&gt;However, during AdminRenderer rendering, the renderer directly invokes:&lt;/p&gt;
&lt;p&gt;view.get(...)&lt;/p&gt;
&lt;p&gt;A view whose permission class explicitly allowed POST but denied GET still executed its GET handler while rendering an invalid POST request through AdminRenderer.&lt;/p&gt;
&lt;p&gt;As a result, data intended to be available only through an authorized GET request was included in the generated HTML response.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;Proof of Concept&lt;/p&gt;
&lt;p&gt;Using a standard ListCreateAP…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-3828</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-73229</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-73229</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 powerful and flexible toolkit for building Web APIs. Prior to 3.17.2, Django REST Framework&amp;#39;s rest_framework/renderers.py AdminRenderer.render() uses override_method() to simulate GET and directly invokes view.get() without view.check_permissions() while rendering an invalid write request, allowing a 400 Bad Request HTML response to disclose data from a GET representation that the requester is not permitted to access. 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 powerful and flexible toolkit for building Web APIs. Prior to 3.17.2, Django REST Framework&amp;#39;s rest_framework/renderers.py AdminRenderer.render() uses override_method() to simulate GET and directly invokes view.get() without view.check_permissions() while rendering an invalid write request, allowing a 400 Bad Request HTML response to disclose data from a GET representation that the requester is not permitted to access. 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-73229</guid>
    </item>
  </channel>
</rss>
