Out-of-bounds Write Affecting vim package, versions *


Severity

Recommended
0.0
medium
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.31% (23rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Out-of-bounds Write vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CENTOS6-VIM-17338146
  • published14 Jun 2026
  • disclosed11 Jun 2026

Introduced: 11 Jun 2026

NewCVE-2026-52859  (opens in a new tab)
CWE-787  (opens in a new tab)

How to fix?

There is no fixed version for Centos:6 vim.

NVD Description

Note: Versions mentioned in the description apply only to the upstream vim package and not the vim package as distributed by Centos. See How to fix? for Centos:6 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1