<?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>Tue, 13 Oct 2026 05:16:23 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-339127</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-339127</link>
      <description>EUVD-2026-339127</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-339127</guid>
    </item>
    <item>
      <title>fkie_cve-2026-47128</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47128</link>
      <description>&lt;p&gt;nono is software that allows users to run AI agents in a zero-latency sandbox. Prior to version 0.55.0, the nono Landlock/seccomp policies allow access to local Unix domain sockets (concrete and abstract). This allows an easy sandbox escape by talking to the per-user systemd dbus socket. Version 0.55.0 patches the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;nono is software that allows users to run AI agents in a zero-latency sandbox. Prior to version 0.55.0, the nono Landlock/seccomp policies allow access to local Unix domain sockets (concrete and abstract). This allows an easy sandbox escape by talking to the per-user systemd dbus socket. Version 0.55.0 patches the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-47128</guid>
    </item>
    <item>
      <title>GHSA-27vp-2mmc-vmh3 — nono: Sandbox escape on Linux via D-Bus: `systemd-run --user`</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-27vp-2mmc-vmh3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: nono-cli&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The nono Landlock/seccomp policies allow access to local Unix domain sockets (concrete and abstract). This allows an easy sandbox escape by talking to the per-user systemd dbus socket.&lt;/p&gt;
&lt;p&gt;Threat scenario: Running Aider, Claude Code, OpenCode or similar tools with &amp;#34;allow bash&amp;#34; policy so that it can invoke arbitrary host tools like `make`, `gcc`, etc. to write code.&lt;/p&gt;
&lt;p&gt;### Reproducer&lt;/p&gt;
&lt;p&gt;Here, instead of running a tool like `opencode` or `claude` one can just invoke `systemd-run`, but this is something an agent could be tricked into doing:&lt;/p&gt;
&lt;p&gt;```bash
$ cd ~/src/myproject
$ nono run -s --allow-cwd --profile claude-code -- \
      systemd-run --user -q --wait --collect \
      /bin/sh -c &amp;#34;echo oops &amp;gt; ~/Documents/escaped.txt&amp;#34;
$ cat /var/home/test/Documents/escaped.txt
oops
$
```&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Complete sandbox escape. The unsandboxed sibling process can write anywhere the user can write, spawn arbitrary processes with network access, etc.&lt;/p&gt;
&lt;p&gt;### Maintainer Context&lt;/p&gt;
&lt;p&gt;This issue allows a process running inside the sandbox to escape confinement by interacting with local user-scoped IPC mechanisms and regain the authority already held by the invoking user or service account.&lt;/p&gt;
&lt;p&gt;The issue impacts the sandbox’s confinement and blast-radius reduction guarantees for agents and sandboxed tooling. However, exploitation does not provide privilege escalation, cross-user access, or host compromise beyond the permissions already available to the launcher outside the sandbox.&lt;/p&gt;
&lt;p&gt;This issue affects t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: nono-cli&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The nono Landlock/seccomp policies allow access to local Unix domain sockets (concrete and abstract). This allows an easy sandbox escape by talking to the per-user systemd dbus socket.&lt;/p&gt;
&lt;p&gt;Threat scenario: Running Aider, Claude Code, OpenCode or similar tools with &amp;#34;allow bash&amp;#34; policy so that it can invoke arbitrary host tools like `make`, `gcc`, etc. to write code.&lt;/p&gt;
&lt;p&gt;### Reproducer&lt;/p&gt;
&lt;p&gt;Here, instead of running a tool like `opencode` or `claude` one can just invoke `systemd-run`, but this is something an agent could be tricked into doing:&lt;/p&gt;
&lt;p&gt;```bash
$ cd ~/src/myproject
$ nono run -s --allow-cwd --profile claude-code -- \
      systemd-run --user -q --wait --collect \
      /bin/sh -c &amp;#34;echo oops &amp;gt; ~/Documents/escaped.txt&amp;#34;
$ cat /var/home/test/Documents/escaped.txt
oops
$
```&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Complete sandbox escape. The unsandboxed sibling process can write anywhere the user can write, spawn arbitrary processes with network access, etc.&lt;/p&gt;
&lt;p&gt;### Maintainer Context&lt;/p&gt;
&lt;p&gt;This issue allows a process running inside the sandbox to escape confinement by interacting with local user-scoped IPC mechanisms and regain the authority already held by the invoking user or service account.&lt;/p&gt;
&lt;p&gt;The issue impacts the sandbox’s confinement and blast-radius reduction guarantees for agents and sandboxed tooling. However, exploitation does not provide privilege escalation, cross-user access, or host compromise beyond the permissions already available to the launcher outside the sandbox.&lt;/p&gt;
&lt;p&gt;This issue affects t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-27vp-2mmc-vmh3</guid>
    </item>
  </channel>
</rss>
