<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T04:52:56.469892+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-61592</id>
    <title>CVE-2026-61592 — djust: SSE sessions are not bound to the authenticated user; the client-chosen session_id is the sole authorization cap…</title>
    <updated>2026-10-02T04:52:56.472009+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> djust-org djust</p>
<p>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'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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-61592"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-f795-p5jw-j6g2</id>
    <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>
    <updated>2026-10-02T04:52:56.472077+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: djust</p>
<p>### 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's identity and state**.</p>
<p>### 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.</p>
<p>### Workarounds
Disable the SSE transport short of upgrading.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-f795-p5jw-j6g2"/>
  </entry>
</feed>
