cve.bz

CVE-2026-73075 vim vim: Buffer Underrun

4.6 mediumEPSS 0.09%Fix available

Medium (4.6) in vim vim. EPSS 0.09% estimated probability of exploitation activity in the next 30 days.

On this page
Vim is an open source, command line text editor. From 9.2.0469 until 9.2.0843, popup_mark_opacity_zindex() in src/popupwin.c can use a negative w_winrow for a text-property-anchored popup with clipwindow and opacity, indexing before the screen array instead of accounting for w_popup_topoff and causing an out-of-bounds read and conditional write. This issue is fixed in version 9.2.0843.

Severity

CVSS 4.0

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

CVSS 3.1

3.9 low
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
EPSS
0.09% (unchanged from 0.09% a week ago; 0.09% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-15. 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-08-11. 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-124 Buffer Underwrite (Buffer Underrun)
CWE-125 Out-of-bounds Read
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-73075 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-73075?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-73075?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-73075 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.

Badge for a README or a site

CVE-2026-73075

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-73075](https://cve.bz/cve/badge/CVE-2026-73075.svg)](https://cve.bz/cve/CVE-2026-73075)

HTML:

<a href="https://cve.bz/cve/CVE-2026-73075"><img src="https://cve.bz/cve/badge/CVE-2026-73075.svg" alt="CVE-2026-73075"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
vim:vimfrom 9.2.0469 before 9.2.0843

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14vim2:9.2.0858-1DEBIAN-CVE-2026-73075
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.0957-150000.5.102.1SUSE-SU-2026:3679-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Micro 5.5 and 6 morevim9.2.0957-150500.20.64.1SUSE-SU-2026:3680-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5vim9.2.0957-17.76.1SUSE-SU-2026:3677-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0vim9.2.0957-160000.1.1SUSE-SU-2026:23552-1
SUSELinux Micro 6.0vim9.2.0957-1.1SUSE-SU-2026:23365-1
SUSELinux Micro 6.1vim9.2.0957-slfo.1.1_1.1SUSE-SU-2026:23190-1
SUSELinux Micro 6.2vim9.2.0957-160000.1.1SUSE-SU-2026:23393-1
SUSELinux Micro Extras 6.2vim9.2.0957-160000.1.1SUSE-SU-2026:23391-1
openSUSELeap 16.0vim9.2.0957-160000.1.1openSUSE-SU-2026:21671-1
Alpinev3.23vim9.2.0854-r0ALPINE-CVE-2026-73075
Alpinev3.24vim9.2.0843-r0ALPINE-CVE-2026-73075
Azure Linux3vim9.2.0957-1AZL-95973
Alpaquita23, 25, streamvim9.2.0854-r0BELL-CVE-2026-73075

From the distributions' data via OSV.dev: the Debian Security Tracker; 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 · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Moderate: This flaw in Vim involves an out-of-bounds memory access during popup opacity handling. Exploitation requires a local attacker to execute specially crafted Vim script that utilizes specific popup window features, making user interaction a prerequisite. The impact is typically limited to an out-of-bounds read and a constrained write, which may lead to unexpected behavior but is not expected to result in immediate system compromise or arbitrary code execution.

None of the Red Hat products ship this vulnerable code. Hence, are not affected.

Red Hat's mitigation

To mitigate this issue, users should avoid running untrusted Vim scripts or installing untrusted plugins. This vulnerability is triggered by the execution of malicious Vim script code, not merely by opening a file.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10vimNot affected
Red Hat Enterprise Linux 6vimNot affected
Red Hat Enterprise Linux 7vimNot affected
Red Hat Enterprise Linux 8vimNot affected
Red Hat Enterprise Linux 9vimNot affected
Red Hat Hardened ImagesvimNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not affected

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-73075.

Attack patterns (CAPEC)

  • CAPEC-540 Overread Buffers Likelihood: Low · Severity: High

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

References

Check your stackJSON