Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-52859: Vim: Out-of-bounds Read in Terminal Screen Snapshot

Noroxi assessment

Priority: Monitor (action score 27/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: vim vim 9.2.0565; azl3 vim 9.2.0488-1 on Azure Linux 3.0 9.2.0620-1.

Low priority for now. Upgrade to vim vim 9.2.0565; azl3 vim 9.2.0488-1 on Azure Linux 3.0 9.2.0620-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.9 · v4.0—No exploit Fix available
Published
Jun 11, 2026
Updated
Jun 17, 2026
EPSS
0.3% · 22th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
27 / 40 · 6.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
6.9
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-52859

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for vim records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
vimvim

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • vim vimbefore 9.2.0565

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • vim vim

    • < 9.2.0565affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10vim-commonbefore 2:9.1.083-9.el10_2.202:9.1.083-9.el10_2.20
AlmaLinux:10vim-databefore 2:9.1.083-9.el10_2.202:9.1.083-9.el10_2.20
AlmaLinux:10vim-enhancedbefore 2:9.1.083-9.el10_2.202:9.1.083-9.el10_2.20
AlmaLinux:10vim-filesystembefore 2:9.1.083-9.el10_2.202:9.1.083-9.el10_2.20
AlmaLinux:10vim-minimalbefore 2:9.1.083-9.el10_2.202:9.1.083-9.el10_2.20
AlmaLinux:10vim-X11before 2:9.1.083-9.el10_2.202:9.1.083-9.el10_2.20
AlmaLinux:10xxdbefore 2:9.1.083-9.el10_2.202:9.1.083-9.el10_2.20
AlmaLinux:8vim-commonbefore 2:8.0.1763-31.el8_10.72:8.0.1763-31.el8_10.7
AlmaLinux:8vim-enhancedbefore 2:8.0.1763-31.el8_10.72:8.0.1763-31.el8_10.7
AlmaLinux:8vim-filesystembefore 2:8.0.1763-31.el8_10.72:8.0.1763-31.el8_10.7
AlmaLinux:8vim-minimalbefore 2:8.0.1763-31.el8_10.72:8.0.1763-31.el8_10.7
AlmaLinux:8vim-X11before 2:8.0.1763-31.el8_10.72:8.0.1763-31.el8_10.7
AlmaLinux:9vim-commonbefore 2:8.2.2637-26.el9_8.212:8.2.2637-26.el9_8.21
AlmaLinux:9vim-enhancedbefore 2:8.2.2637-26.el9_8.212:8.2.2637-26.el9_8.21
AlmaLinux:9vim-filesystembefore 2:8.2.2637-26.el9_8.212:8.2.2637-26.el9_8.21
AlmaLinux:9vim-minimalbefore 2:8.2.2637-26.el9_8.212:8.2.2637-26.el9_8.21
AlmaLinux:9vim-X11before 2:8.2.2637-26.el9_8.212:8.2.2637-26.el9_8.21
Alpine:v3.23vimbefore 9.2.0567-r09.2.0567-r0
Debian:12vimfrom 0—
Debian:14vimbefore 2:9.2.0782-12:9.2.0782-1
Red Hat:enterprise_linux:10.2vimbefore 2:9.1.083-9.el10_2.202:9.1.083-9.el10_2.20
Red Hat:enterprise_linux:10.2vim-commonbefore 2:9.1.083-9.el10_2.202:9.1.083-9.el10_2.20
Red Hat:enterprise_linux:10.2vim-enhancedbefore 2:9.1.083-9.el10_2.202:9.1.083-9.el10_2.20
Red Hat:enterprise_linux:10.2vim-X11before 2:9.1.083-9.el10_2.202:9.1.083-9.el10_2.20

+20

Same product

vim: all records

Other highest-scoring records for the same primary product.

  • CVE-2008-2712Vim 7.1.314, 6.4, and other versions allows user-assisted remote attackers to execute arbitrary commands via Vim scripts that do not properl
    42Plan
  • CVE-2022-0318Heap-based Buffer Overflow in vim/vim
    40Plan
  • CVE-2019-12735getchar.c in Vim before 8.1.1365 and Neovim before 0.3.6 allows remote attackers to execute arbitrary OS commands via the :source! command i
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-47167Jun 11, 2026 · Vim: Vimscript Code Injection in cucumber filetype plugin via crafted step-definition regex
    20Monitor
  • ← EarlierCVE-2026-52858Jun 11, 2026 · Vim: Arbitrary Code Execution via Python Omni-Completion
    29Monitor
  • Later →CVE-2026-52860Jun 11, 2026 · Vim: Arbitrary Code Execution via Python Omni-Completion
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
vim vim9.2.0565 · descriptionVendor (CNA)
azl3 vim 9.2.0488-1 on Azure Linux 3.09.2.0620-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:vim-common2:9.1.083-9.el10_2.20 · AlmaLinux:10Package registry (OSV)
almalinux:vim-data2:9.1.083-9.el10_2.20 · AlmaLinux:10Package registry (OSV)
almalinux:vim-enhanced2:9.1.083-9.el10_2.20 · AlmaLinux:10Package registry (OSV)
almalinux:vim-filesystem2:9.1.083-9.el10_2.20 · AlmaLinux:10Package registry (OSV)
almalinux:vim-minimal2:9.1.083-9.el10_2.20 · AlmaLinux:10Package registry (OSV)
almalinux:vim-X112:9.1.083-9.el10_2.20 · AlmaLinux:10Package registry (OSV)
almalinux:xxd2:9.1.083-9.el10_2.20 · AlmaLinux:10Package registry (OSV)
alpine:vim9.2.0567-r0 · Alpine:v3.23Package registry (OSV)
debian:vim2:9.2.0782-1 · Debian:14Package registry (OSV)
red hat:vim0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-common0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-data0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-default-editor0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-enhanced0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-filesystem0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-minimal0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-X110:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:xxd0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
rocky linux:vim2:9.1.083-9.el10_2.20 · Rocky Linux:10Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-5745414 days apartVim: Out-of-bounds Read with Text Properties
    27Monitor
  • CVE-2026-5745114 days apartVim: Out-of-bounds Read in Text Property Count
    24Monitor
  • CVE-2026-5745214 days apartVim: Out-of-bounds Read with libsodium-encrypted Files
    22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records