<?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>Fri, 02 Oct 2026 22:02:58 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-369657</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-369657</link>
      <description>EUVD-2026-369657</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-369657</guid>
    </item>
    <item>
      <title>fkie_cve-2026-61590</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-61590</link>
      <description>&lt;p&gt;djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, djust&amp;#39;s observability endpoints expose live view/session state and a remote method-invocation surface (`eval_handler`). The localhost restriction was an opt-in middleware that the documented setup omits; the views themselves enforced only `DEBUG`. In the misconfigured-but-documented scenario (DEBUG on, middleware not installed) a non-localhost client could read live application state and invoke handlers remotely. This issue is fixed in djust 1.0.7. The localhost restriction is enforced in-view on every observability endpoint (no longer dependent on a separately-installed middleware), and `eval_handler` is restricted; gated requests receive a non-disclosing response. As a workaround, ensure `DEBUG=False` in production, and do not expose the observability endpoints to untrusted networks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, djust&amp;#39;s observability endpoints expose live view/session state and a remote method-invocation surface (`eval_handler`). The localhost restriction was an opt-in middleware that the documented setup omits; the views themselves enforced only `DEBUG`. In the misconfigured-but-documented scenario (DEBUG on, middleware not installed) a non-localhost client could read live application state and invoke handlers remotely. This issue is fixed in djust 1.0.7. The localhost restriction is enforced in-view on every observability endpoint (no longer dependent on a separately-installed middleware), and `eval_handler` is restricted; gated requests receive a non-disclosing response. As a workaround, ensure `DEBUG=False` in production, and do not expose the observability endpoints to untrusted networks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-61590</guid>
    </item>
    <item>
      <title>GHSA-8g2f-g3gq-5rjv — djust's observability endpoints are network-exposed: the localhost gate is an opt-in middleware the docs omit, and the…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8g2f-g3gq-5rjv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: djust&lt;/p&gt;
&lt;p&gt;### Impact
djust&amp;#39;s observability endpoints expose live view/session state and a remote method-invocation surface (`eval_handler`). The localhost restriction was an **opt-in middleware that the documented setup omits**; the views themselves enforced only `DEBUG`. In the misconfigured-but-documented scenario (DEBUG on, middleware not installed) a non-localhost client could read live application state and invoke handlers remotely.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in **djust 1.0.7**. The localhost restriction is enforced **in-view** on every observability endpoint (no longer dependent on a separately-installed middleware), and `eval_handler` is restricted; gated requests receive a non-disclosing response.&lt;/p&gt;
&lt;p&gt;### Workarounds
Ensure `DEBUG=False` in production, and do not expose the observability endpoints to untrusted networks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: djust&lt;/p&gt;
&lt;p&gt;### Impact
djust&amp;#39;s observability endpoints expose live view/session state and a remote method-invocation surface (`eval_handler`). The localhost restriction was an **opt-in middleware that the documented setup omits**; the views themselves enforced only `DEBUG`. In the misconfigured-but-documented scenario (DEBUG on, middleware not installed) a non-localhost client could read live application state and invoke handlers remotely.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in **djust 1.0.7**. The localhost restriction is enforced **in-view** on every observability endpoint (no longer dependent on a separately-installed middleware), and `eval_handler` is restricted; gated requests receive a non-disclosing response.&lt;/p&gt;
&lt;p&gt;### Workarounds
Ensure `DEBUG=False` in production, and do not expose the observability endpoints to untrusted networks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8g2f-g3gq-5rjv</guid>
    </item>
    <item>
      <title>PYSEC-2026-4039 — djust's observability endpoints are network-exposed: the localhost gate is an opt-in middleware the docs omit, and the…</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-4039</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: djust&lt;/p&gt;
&lt;p&gt;### Impact
djust&amp;#39;s observability endpoints expose live view/session state and a remote method-invocation surface (`eval_handler`). The localhost restriction was an **opt-in middleware that the documented setup omits**; the views themselves enforced only `DEBUG`. In the misconfigured-but-documented scenario (DEBUG on, middleware not installed) a non-localhost client could read live application state and invoke handlers remotely.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in **djust 1.0.7**. The localhost restriction is enforced **in-view** on every observability endpoint (no longer dependent on a separately-installed middleware), and `eval_handler` is restricted; gated requests receive a non-disclosing response.&lt;/p&gt;
&lt;p&gt;### Workarounds
Ensure `DEBUG=False` in production, and do not expose the observability endpoints to untrusted networks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: djust&lt;/p&gt;
&lt;p&gt;### Impact
djust&amp;#39;s observability endpoints expose live view/session state and a remote method-invocation surface (`eval_handler`). The localhost restriction was an **opt-in middleware that the documented setup omits**; the views themselves enforced only `DEBUG`. In the misconfigured-but-documented scenario (DEBUG on, middleware not installed) a non-localhost client could read live application state and invoke handlers remotely.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in **djust 1.0.7**. The localhost restriction is enforced **in-view** on every observability endpoint (no longer dependent on a separately-installed middleware), and `eval_handler` is restricted; gated requests receive a non-disclosing response.&lt;/p&gt;
&lt;p&gt;### Workarounds
Ensure `DEBUG=False` in production, and do not expose the observability endpoints to untrusted networks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-4039</guid>
    </item>
  </channel>
</rss>
