<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-09T18:07:22.732536+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2026-52859</id>
    <title>CVE-2026-52859 — Vim: Out-of-bounds Read in Terminal Screen Snapshot</title>
    <updated>2026-10-09T18:07:23.184049+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> vim</p>
<p>Vim is an open source, command line text editor. Prior to version 9.2.0565, the update_snapshot() function in src/terminal.c copies the visible terminal screen into the scrollback buffer when a snapshot is taken. For each screen cell it walks the cell's chars[] array with no upper bound, stopping only when it encounters a NUL terminator. When a cell legitimately fills all VTERM_MAX_CHARS_PER_CELL (6) slots — a base character plus five combining marks — the bundled libvterm returns the array without a terminating NUL, so the loop reads past the fixed six-element array and appends the out-of-bounds values to a buffer reserved for only six characters. A program whose output is rendered inside a :terminal window can trigger this with a short byte sequence and no Vim scripting, leading to a crash. This issue has been patched in version 9.2.0565.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-52859"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-8451-1</id>
    <title>USN-8451-1 — vim vulnerabilities</title>
    <updated>2026-10-09T18:07:23.184248+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: vim, Ubuntu:Pro:16.04:LTS: vim, Ubuntu:Pro:18.04:LTS: vim, Ubuntu:Pro:20.04:LTS: vim, Ubuntu:22.04:LTS: vim, Ubuntu:24.04:LTS: vim, Ubuntu:25.10: vim, Ubuntu:26.04:LTS: vim</p>
<p>Srinivas Piskala Ganesh Babu discovered that Vim incorrectly handled
directory names when serializing browsed paths to the netrw history file.
An attacker could possibly use this issue to execute arbitrary code.
(CVE-2026-47162)</p>
<p>It was discovered that Vim incorrectly handled step-definition patterns in
the cucumber filetype plugin. An attacker could possibly use this issue to
execute arbitrary code. (CVE-2026-47167)</p>
<p>It was discovered that Vim incorrectly handled import statements during
Python omni-completion. An attacker could possibly use this issue to
execute arbitrary code. (CVE-2026-52858)</p>
<p>Andrej Tomči discovered that Vim incorrectly handled certain terminal
screen cells when taking a snapshot, leading to an out-of-bounds read. An
attacker could possibly use this issue to cause Vim to crash, resulting in
a denial of service. (CVE-2026-52859)</p>
<p>David Carliez discovered that Vim incorrectly handled reconstructed
function and class definitions during Python omni-completion. An attacker
could possibly use this issue to execute arbitrary code. (CVE-2026-52860)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/usn-8451-1"/>
  </entry>
</feed>
