<?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-11-16T23:14:24.618351+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-405822</id>
    <title>EUVD-2026-405822</title>
    <updated>2026-11-16T23:14:24.621153+00:00</updated>
    <content>EUVD-2026-405822</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-405822"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-128321</id>
    <title>fkie_cve-2026-128321</title>
    <updated>2026-11-16T23:14:24.621185+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Tight JPEG decoding in TightVNC and UltraVNC viewers contains a heap-based buffer overflow because an attacker-controlled framebuffer rectangle width is not validated against a fixed-size decoding buffer. A malicious VNC server can cause an out-of-bounds heap write when a user connects, resulting in application crash and potentially other memory-corruption impacts.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-128321"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-2v2r-xq5w-26rm</id>
    <title>GHSA-2v2r-xq5w-26rm</title>
    <updated>2026-11-16T23:14:24.621218+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Tight JPEG decoding in TightVNC and UltraVNC viewers contains a heap-based buffer overflow because an attacker-controlled framebuffer rectangle width is not validated against a fixed-size decoding buffer. A malicious VNC server can cause an out-of-bounds heap write when a user connects, resulting in application crash and potentially other memory-corruption impacts.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-2v2r-xq5w-26rm"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-128321</id>
    <title>UBUNTU-CVE-2026-128321</title>
    <updated>2026-11-16T23:14:24.621235+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: tightvnc, Ubuntu:16.04:LTS: tightvnc, Ubuntu:18.04:LTS: tightvnc, Ubuntu:20.04:LTS: tightvnc, Ubuntu:22.04:LTS: tightvnc, Ubuntu:24.04:LTS: tightvnc, Ubuntu:26.10: tightvnc, Ubuntu:26.04:LTS: tightvnc</p>
<p>Tight JPEG decoding in TightVNC and UltraVNC viewers contains a heap-based buffer overflow because an attacker-controlled framebuffer rectangle width is not validated against a fixed-size decoding buffer. A malicious VNC server can cause an out-of-bounds heap write when a user connects, resulting in application crash and potentially other memory-corruption impacts.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-128321"/>
  </entry>
</feed>
