<?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-08T14:41:03.348284+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-330144</id>
    <title>EUVD-2026-330144</title>
    <updated>2026-10-08T14:41:03.400503+00:00</updated>
    <content>EUVD-2026-330144</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-330144"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54321</id>
    <title>fkie_cve-2026-54321</title>
    <updated>2026-10-08T14:41:03.400544+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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's visibility changed. This vulnerability is fixed in 0.184.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-54321"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-ww63-pv5x-vfc8</id>
    <title>GHSA-ww63-pv5x-vfc8 — Daytona: Public sandbox previews remain accessible for up to one hour after being made private</title>
    <updated>2026-10-08T14:41:03.400579+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/daytonaio/daytona</p>
<p>### 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's visibility changed.</p>
<p>### Impact
When a sandbox owner changed a preview from public to private, the preview proxy could continue serving unauthenticated requests to that sandbox'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'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.</p>
<p>### Patches
Fixed in v0.184.0. Sandbox visibility changes now invalidate the proxy's cached preview state immediately, so revoking a public preview takes effect on the next request.</p>
<p>### Workarounds
Upgrade to v0.184.0 or later. There is no configuration workaround for earlier versions.</p>
<p>### Credit
Reported through Daytona's Vulnerability Disclosure Program by **mrknightnidu(nidalkhan)**.
**Linkedin**: https://www.linkedin.com/in/mrknight-nidu-031340328/</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-ww63-pv5x-vfc8"/>
  </entry>
</feed>
