<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T09:35:11.686404+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/euvd-2026-370445</id>
    <title>EUVD-2026-370445</title>
    <updated>2026-10-06T09:35:11.689128+00:00</updated>
    <content>EUVD-2026-370445</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-370445"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-61591</id>
    <title>fkie_cve-2026-61591</title>
    <updated>2026-10-06T09:35:11.689163+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, for views that opt into state snapshots, the snapshot `state_json` embedded in the client page was restored on reconnect as trusted view state with no integrity check. A client could edit the unsigned `state_json` in their page and return it in the reconnect mount frame to inject arbitrary view attributes — e.g. flip `is_admin` to `True`, or change `account_id` / `balance` — escalating privilege or tampering with business state held in public view attributes (the normal djust pattern). This issue is fixed in djust 1.0.7. State snapshots are signed; unsigned or forged snapshots are rejected on the back-navigation restore path. As a workaround, do not enable state snapshots; do not hold authorization/ownership state in public view attributes.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-61591"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-c67v-vqrp-m5wj</id>
    <title>GHSA-c67v-vqrp-m5wj — djust: Unsigned client state snapshot is restored as trusted view state (privilege escalation / state injection)</title>
    <updated>2026-10-06T09:35:11.689222+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: djust</p>
<p>### Impact
For views that opt into state snapshots, the snapshot `state_json` embedded in the client page was restored on reconnect as **trusted** view state with no integrity check. A client could edit the unsigned `state_json` in their page and return it in the reconnect mount frame to **inject arbitrary view attributes** — e.g. flip `is_admin` to `True`, or change `account_id` / `balance` — escalating privilege or tampering with business state held in public view attributes (the normal djust pattern).</p>
<p>### Patches
Fixed in **djust 1.0.7**. State snapshots are signed; unsigned or forged snapshots are rejected on the back-navigation restore path.</p>
<p>### Workarounds
Do not enable state snapshots; do not hold authorization/ownership state in public view attributes.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-c67v-vqrp-m5wj"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-4040</id>
    <title>PYSEC-2026-4040 — djust: Unsigned client state snapshot is restored as trusted view state (privilege escalation / state injection)</title>
    <updated>2026-10-06T09:35:11.689281+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: djust</p>
<p>### Impact
For views that opt into state snapshots, the snapshot `state_json` embedded in the client page was restored on reconnect as **trusted** view state with no integrity check. A client could edit the unsigned `state_json` in their page and return it in the reconnect mount frame to **inject arbitrary view attributes** — e.g. flip `is_admin` to `True`, or change `account_id` / `balance` — escalating privilege or tampering with business state held in public view attributes (the normal djust pattern).</p>
<p>### Patches
Fixed in **djust 1.0.7**. State snapshots are signed; unsigned or forged snapshots are rejected on the back-navigation restore path.</p>
<p>### Workarounds
Do not enable state snapshots; do not hold authorization/ownership state in public view attributes.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-4040"/>
  </entry>
</feed>
