<?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://vulnerability.circl.lu</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 18:04:34 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-61592</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-61592</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, SSE sessions were keyed solely by a client-chosen `session_id` with no binding to the authenticated user — a control the WebSocket transport has but that was dropped on SSE. An attacker who learns (or a victim who leaks) a `session_id` could connect to the message endpoint and dispatch event handlers that execute with the victim&amp;#39;s identity and state. This is fixed in djust 1.0.7. Each SSE session is bound to its owning principal at creation and cross-principal access is rejected; SSE session creation is additionally capped per principal. As a workaround, disable the SSE transport.&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, SSE sessions were keyed solely by a client-chosen `session_id` with no binding to the authenticated user — a control the WebSocket transport has but that was dropped on SSE. An attacker who learns (or a victim who leaks) a `session_id` could connect to the message endpoint and dispatch event handlers that execute with the victim&amp;#39;s identity and state. This is fixed in djust 1.0.7. Each SSE session is bound to its owning principal at creation and cross-principal access is rejected; SSE session creation is additionally capped per principal. As a workaround, disable the SSE transport.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-61592</guid>
    </item>
    <item>
      <title>GHSA-f795-p5jw-j6g2 — djust: SSE sessions are not bound to the authenticated user; the client-chosen session_id is the sole authorization cap…</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-f795-p5jw-j6g2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: djust&lt;/p&gt;
&lt;p&gt;### Impact
SSE sessions were keyed solely by a **client-chosen** `session_id` with no binding to the authenticated user — a control the WebSocket transport has but that was dropped on SSE. An attacker who learns (or a victim who leaks) a `session_id` could connect to the message endpoint and dispatch event handlers that execute with the **victim&amp;#39;s identity and state**.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in **djust 1.0.7**. Each SSE session is bound to its owning principal at creation and cross-principal access is rejected; SSE session creation is additionally capped per principal.&lt;/p&gt;
&lt;p&gt;### Workarounds
Disable the SSE transport short of upgrading.&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
SSE sessions were keyed solely by a **client-chosen** `session_id` with no binding to the authenticated user — a control the WebSocket transport has but that was dropped on SSE. An attacker who learns (or a victim who leaks) a `session_id` could connect to the message endpoint and dispatch event handlers that execute with the **victim&amp;#39;s identity and state**.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in **djust 1.0.7**. Each SSE session is bound to its owning principal at creation and cross-principal access is rejected; SSE session creation is additionally capped per principal.&lt;/p&gt;
&lt;p&gt;### Workarounds
Disable the SSE transport short of upgrading.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-f795-p5jw-j6g2</guid>
    </item>
    <item>
      <title>PYSEC-2026-4043 — djust: SSE sessions are not bound to the authenticated user; the client-chosen session_id is the sole authorization cap…</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-4043</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: djust&lt;/p&gt;
&lt;p&gt;### Impact
SSE sessions were keyed solely by a **client-chosen** `session_id` with no binding to the authenticated user — a control the WebSocket transport has but that was dropped on SSE. An attacker who learns (or a victim who leaks) a `session_id` could connect to the message endpoint and dispatch event handlers that execute with the **victim&amp;#39;s identity and state**.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in **djust 1.0.7**. Each SSE session is bound to its owning principal at creation and cross-principal access is rejected; SSE session creation is additionally capped per principal.&lt;/p&gt;
&lt;p&gt;### Workarounds
Disable the SSE transport short of upgrading.&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
SSE sessions were keyed solely by a **client-chosen** `session_id` with no binding to the authenticated user — a control the WebSocket transport has but that was dropped on SSE. An attacker who learns (or a victim who leaks) a `session_id` could connect to the message endpoint and dispatch event handlers that execute with the **victim&amp;#39;s identity and state**.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in **djust 1.0.7**. Each SSE session is bound to its owning principal at creation and cross-principal access is rejected; SSE session creation is additionally capped per principal.&lt;/p&gt;
&lt;p&gt;### Workarounds
Disable the SSE transport short of upgrading.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-4043</guid>
    </item>
  </channel>
</rss>
