<?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>Mon, 16 Nov 2026 23:22:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-115392 — Wasmtime before 24.0.13, 25.0.0 before 36.0.14, 37.0.0 before 46.0.3, and 47.0.0 before 47.0.4 Sandbox Escape via Trail…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-115392</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; bytecodealliance wasmtime&lt;/p&gt;
&lt;p&gt;Wasmtime before 24.0.13, 25.0.0 before 36.0.14, 37.0.0 before 46.0.3, and 47.0.0 before 47.0.4 allows a filesystem sandbox escape in wasmtime-wasi because its cap-std dependency mishandles symlinks with trailing slashes on macOS and Linux kernels lacking openat2. A guest with write access to any sandboxed directory can read and write any host-accessible file, and read-only guests may read host files via preexisting symlinks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; bytecodealliance wasmtime&lt;/p&gt;
&lt;p&gt;Wasmtime before 24.0.13, 25.0.0 before 36.0.14, 37.0.0 before 46.0.3, and 47.0.0 before 47.0.4 allows a filesystem sandbox escape in wasmtime-wasi because its cap-std dependency mishandles symlinks with trailing slashes on macOS and Linux kernels lacking openat2. A guest with write access to any sandboxed directory can read and write any host-accessible file, and read-only guests may read host files via preexisting symlinks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-115392</guid>
    </item>
    <item>
      <title>RUSTSEC-2026-0482 — Paths or symlinks ending in a slash escape the sandbox</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2026-0482</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: cap-primitives&lt;/p&gt;
&lt;p&gt;cap-primitives resolves a path inside a sandboxed directory one component at a time and opens the last component with `O_NOFOLLOW`, so that a symlink there cannot lead out of the directory. When the path ended in `/`, the resolver added the slash back to the last component before opening it. With a trailing slash the operating system no longer treats that component as the last one, so `O_NOFOLLOW` does not apply, the symlink is followed, and the resulting file descriptor was returned without further checks.&lt;/p&gt;
&lt;p&gt;A symlink inside the sandbox that points outside it, such as `escape -&amp;gt; ../outside` or a link to `/`, can therefore be opened as `escape/`. If the symlink&amp;#39;s own target ends in `/`, the caller&amp;#39;s path does not need a trailing slash at all, so removing trailing slashes from untrusted input is not a workaround. The maintainers&amp;#39; advisory reports reads and writes outside the sandbox through `open`, `open_dir`, `read_dir` and `canonicalize`, and directory creation, removal and renames outside it through `create_dir`, `remove_dir` and `rename`.&lt;/p&gt;
&lt;p&gt;This resolver is used on Windows and macOS, on FreeBSD when `O_RESOLVE_BENEATH` is not available, and on Linux when `openat2` is not available (kernels before 5.6, or a seccomp policy that rejects it). cap-std and other crates built on cap-primitives are affected through it. Wasmtime&amp;#39;s WASI filesystem support was affected as well; that is covered by RUSTSEC-2026-0269.&lt;/p&gt;
&lt;p&gt;The fix stops re-adding the trailing slash and is in 3.4.6 and 4.0.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: cap-primitives&lt;/p&gt;
&lt;p&gt;cap-primitives resolves a path inside a sandboxed directory one component at a time and opens the last component with `O_NOFOLLOW`, so that a symlink there cannot lead out of the directory. When the path ended in `/`, the resolver added the slash back to the last component before opening it. With a trailing slash the operating system no longer treats that component as the last one, so `O_NOFOLLOW` does not apply, the symlink is followed, and the resulting file descriptor was returned without further checks.&lt;/p&gt;
&lt;p&gt;A symlink inside the sandbox that points outside it, such as `escape -&amp;gt; ../outside` or a link to `/`, can therefore be opened as `escape/`. If the symlink&amp;#39;s own target ends in `/`, the caller&amp;#39;s path does not need a trailing slash at all, so removing trailing slashes from untrusted input is not a workaround. The maintainers&amp;#39; advisory reports reads and writes outside the sandbox through `open`, `open_dir`, `read_dir` and `canonicalize`, and directory creation, removal and renames outside it through `create_dir`, `remove_dir` and `rename`.&lt;/p&gt;
&lt;p&gt;This resolver is used on Windows and macOS, on FreeBSD when `O_RESOLVE_BENEATH` is not available, and on Linux when `openat2` is not available (kernels before 5.6, or a seccomp policy that rejects it). cap-std and other crates built on cap-primitives are affected through it. Wasmtime&amp;#39;s WASI filesystem support was affected as well; that is covered by RUSTSEC-2026-0269.&lt;/p&gt;
&lt;p&gt;The fix stops re-adding the trailing slash and is in 3.4.6 and 4.0.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2026-0482</guid>
    </item>
  </channel>
</rss>
