<?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-07T11:36:04.631905+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/bdu:2025-10399</id>
    <title>bdu:2025-10399</title>
    <updated>2026-10-07T11:36:04.635042+00:00</updated>
    <content>bdu:2025-10399</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-10399"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-229320</id>
    <title>EUVD-2026-229320</title>
    <updated>2026-10-07T11:36:04.635073+00:00</updated>
    <content>EUVD-2026-229320</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-229320"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-32428</id>
    <title>fkie_cve-2025-32428</title>
    <updated>2026-10-07T11:36:04.635087+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Jupyter Remote Desktop Proxy allows you to run a Linux Desktop on a JupyterHub. jupyter-remote-desktop-proxy was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by jupyter-remote-desktop-proxy were still accessible via the network. This vulnerability does not affect users having TurboVNC as the vncserver executable. This issue is fixed in 3.0.1.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-32428"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vrq4-9hc3-cgp7</id>
    <title>GHSA-vrq4-9hc3-cgp7 — TigerVNC accessible via the network and not just via a UNIX socket as intended</title>
    <updated>2026-10-07T11:36:04.635118+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: jupyter-remote-desktop-proxy</p>
<p>## Summary</p>
<p>`jupyter-remote-desktop-proxy` was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by `jupyter-remote-desktop-proxy` were still accessible via the network.</p>
<p>This vulnerability does not affect users having TurboVNC as the `vncserver` executable.</p>
<p>## Credits</p>
<p>This vulnerability was identified by Arne Gottwald at University of Göttingen and analyzed, reported, and reviewed by @frejanordsiek.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vrq4-9hc3-cgp7"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-365</id>
    <title>PYSEC-2026-365 — TigerVNC accessible via the network and not just via a UNIX socket as intended</title>
    <updated>2026-10-07T11:36:04.635146+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: jupyter-remote-desktop-proxy</p>
<p>## Summary</p>
<p>`jupyter-remote-desktop-proxy` was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by `jupyter-remote-desktop-proxy` were still accessible via the network.</p>
<p>This vulnerability does not affect users having TurboVNC as the `vncserver` executable.</p>
<p>## Credits</p>
<p>This vulnerability was identified by Arne Gottwald at University of Göttingen and analyzed, reported, and reviewed by @frejanordsiek.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-365"/>
  </entry>
</feed>
