cve.bz

CVE-2026-45130 Heap-based Buffer Overflow

5.5 mediumExploit referenceEPSS 0.2%Fix available

Medium (5.5). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Vim is an open source, command line text editor. Prior to version 9.2.0450, a heap buffer overflow exists in read_compound() in src/spellfile.c when loading a crafted spell file (.spl) with UTF-8 encoding active. An attacker-controlled length field in the spell file's compound section overflows a 32-bit signed integer multiplication, causing a small buffer to be allocated for a write loop that runs many iterations, overflowing the heap. Because the 'spelllang' option can be set from a modeline, a text file modeline can trigger spell file loading if a malicious .spl file has been planted on the runtimepath. This issue has been patched in version 9.2.0450.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-122 Heap-based Buffer Overflow
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-45130 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-45130?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-45130?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-45130 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
neovim:neovimthrough 0.12.2
vim:vimbefore 9.2.0450

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12vimno fix listedDEBIAN-CVE-2026-45130
Debian13vim2:9.1.1230-2+deb13u1DEBIAN-CVE-2026-45130 DSA-6600-1
Debian14vim2:9.2.0461-1DEBIAN-CVE-2026-45130
Ubuntu22.04:LTSvim2:8.2.3995-1ubuntu2.30UBUNTU-CVE-2026-45130 USN-8304-1
Ubuntu24.04:LTSvim2:9.1.0016-1ubuntu7.14UBUNTU-CVE-2026-45130 USN-8304-1
Ubuntu25.10vim2:9.1.0967-1ubuntu6.5UBUNTU-CVE-2026-45130 USN-8304-1
Ubuntu26.04:LTSvim2:9.1.2141-1ubuntu4.2UBUNTU-CVE-2026-45130 USN-8304-1
UbuntuPro:14.04:LTSvim2:7.4.052-1ubuntu3.1+esm26UBUNTU-CVE-2026-45130 USN-8304-1
UbuntuPro:16.04:LTSvim2:7.4.1689-3ubuntu1.5+esm32UBUNTU-CVE-2026-45130 USN-8304-1
UbuntuPro:18.04:LTSvim2:8.0.1453-1ubuntu1.13+esm17UBUNTU-CVE-2026-45130 USN-8304-1
UbuntuPro:20.04:LTSvim2:8.1.2269-1ubuntu5.32+esm5UBUNTU-CVE-2026-45130 USN-8304-1
Red Hathummingbird:1vim, xxd, vim-X11 and 6 more2:9.2.967-1.1.hum1RHSA-2026:57614
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise Micro 5.3 and 3 morevim9.2.0530-150000.5.94.1SUSE-SU-2026:2313-1
SUSELinux Micro Extras 6.2vim9.2.0530-160000.1.1SUSE-SU-2026:21833-1
openSUSETumbleweedvim9.2.0530-1.1openSUSE-SU-2026:11114-1
Alpinev3.23, v3.24vim9.2.0452-r0ALPINE-CVE-2026-45130
Azure Linux3vim9.2.0461-1AZL-86246
Alpaquita23, 25, streamvim9.2.0452-r0BELL-CVE-2026-45130

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This Moderate flaw in Vim arises from a heap buffer overflow when processing specially crafted spell files with UTF-8 encoding. Exploitation requires user interaction, specifically opening a text file containing a malicious modeline that points to a planted, malicious spell file. This limits the attack vector to scenarios where an attacker can control both the text file and the spell file on the user's system, leading primarily to application-level denial of service.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Hardened Imagesvim-main-9.2.967-1.1.hum1Fixed 2026-08-20RHSA-2026:57614
Red Hat Enterprise Linux 10vimFix deferred
Red Hat Enterprise Linux 6vimOut of support scope
Red Hat Enterprise Linux 7vimFix deferred
Red Hat Enterprise Linux 8vimFix deferred
Red Hat Enterprise Linux 9vimFix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-dashboard-rhel9Under investigation
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-45130.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON