<?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>Thu, 08 Oct 2026 20:49:08 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-330144</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-330144</link>
      <description>EUVD-2026-330144</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-330144</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54321</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54321</link>
      <description>&lt;p&gt;Daytona is a secure and elastic infrastructure runtime for AI-generated code execution and agent workflows. From 0.101.0 until 0.184.0, sandbox previews that were switched from public to private could remain reachable without authentication for a short period after the change, due to a cached visibility state that was not invalidated when the sandbox&amp;#39;s visibility changed. This vulnerability is fixed in 0.184.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Daytona is a secure and elastic infrastructure runtime for AI-generated code execution and agent workflows. From 0.101.0 until 0.184.0, sandbox previews that were switched from public to private could remain reachable without authentication for a short period after the change, due to a cached visibility state that was not invalidated when the sandbox&amp;#39;s visibility changed. This vulnerability is fixed in 0.184.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54321</guid>
    </item>
    <item>
      <title>GHSA-ww63-pv5x-vfc8 — Daytona: Public sandbox previews remain accessible for up to one hour after being made private</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ww63-pv5x-vfc8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/daytonaio/daytona&lt;/p&gt;
&lt;p&gt;### Summary
Sandbox previews that were switched from public to private could remain reachable without authentication for a short period after the change, due to a cached visibility state that was not invalidated when the sandbox&amp;#39;s visibility changed.&lt;/p&gt;
&lt;p&gt;### Impact
When a sandbox owner changed a preview from public to private, the preview proxy could continue serving unauthenticated requests to that sandbox&amp;#39;s ordinary preview ports for a bounded period before the change took effect. Only sandboxes that had been made public and were later set back to private were affected, and only until the proxy&amp;#39;s cached visibility state was refreshed. Terminal, toolbox, and recording-dashboard ports were never affected, as those always require authentication. The issue did not involve cross-tenant access, privilege escalation, or remote code execution.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in v0.184.0. Sandbox visibility changes now invalidate the proxy&amp;#39;s cached preview state immediately, so revoking a public preview takes effect on the next request.&lt;/p&gt;
&lt;p&gt;### Workarounds
Upgrade to v0.184.0 or later. There is no configuration workaround for earlier versions.&lt;/p&gt;
&lt;p&gt;### Credit
Reported through Daytona&amp;#39;s Vulnerability Disclosure Program by **mrknightnidu(nidalkhan)**.
**Linkedin**: https://www.linkedin.com/in/mrknight-nidu-031340328/&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/daytonaio/daytona&lt;/p&gt;
&lt;p&gt;### Summary
Sandbox previews that were switched from public to private could remain reachable without authentication for a short period after the change, due to a cached visibility state that was not invalidated when the sandbox&amp;#39;s visibility changed.&lt;/p&gt;
&lt;p&gt;### Impact
When a sandbox owner changed a preview from public to private, the preview proxy could continue serving unauthenticated requests to that sandbox&amp;#39;s ordinary preview ports for a bounded period before the change took effect. Only sandboxes that had been made public and were later set back to private were affected, and only until the proxy&amp;#39;s cached visibility state was refreshed. Terminal, toolbox, and recording-dashboard ports were never affected, as those always require authentication. The issue did not involve cross-tenant access, privilege escalation, or remote code execution.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in v0.184.0. Sandbox visibility changes now invalidate the proxy&amp;#39;s cached preview state immediately, so revoking a public preview takes effect on the next request.&lt;/p&gt;
&lt;p&gt;### Workarounds
Upgrade to v0.184.0 or later. There is no configuration workaround for earlier versions.&lt;/p&gt;
&lt;p&gt;### Credit
Reported through Daytona&amp;#39;s Vulnerability Disclosure Program by **mrknightnidu(nidalkhan)**.
**Linkedin**: https://www.linkedin.com/in/mrknight-nidu-031340328/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ww63-pv5x-vfc8</guid>
    </item>
  </channel>
</rss>
