CVE-2022-2129 | Out-of-bounds Write in vim/vim

Exp

Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.

Published: 2022-06-19 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-2129 is rated High Exploit Risk (70.1/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.35%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-2129

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-2129

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-07-06 1.34% 1.35% +0.01%
2 2026-06-16 1.11% 1.34% +0.24%
3 2026-06-15 — 1.11% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-2129

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
7.8 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2022-2129

OS Trackers for CVE-2022-2129

vendor priority summary link
alpine — CVE-2022-2129: 1 source package rows (vim); 97 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 90. https://security.alpinelinux.org/vuln/CVE-2022-2129
debian not yet assigned CVE-2022-2129 not yet assigned priority: Debian including 1 source packages (vim), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-2129
gentoo low CVE-2022-2129: 2 GLSA(s) (202208-32, 202305-16), 3 atom(s) (app-editors/gvim, app-editors/vim, app-editors/vim-core); latest impact low. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-2129
redhat low — https://access.redhat.com/security/cve/CVE-2022-2129
suse low CVE-2022-2129 severity low: SUSE including 289 source package names (11.1-2.2.281:vim-9.0.0313-150000.5.25.1, 11.1-2.2.281:vim-data-common-9.0.0313-150000.5.25.1, …), 722 product×package rows across 202 product lines (Container ses/7.1/ceph/haproxy, Container suse/sle-micro-rancher/5.2, … (202 product lines)): Fixed 608, Known Affected 94, Known Not Affected 20. https://www.suse.com/security/cve/CVE-2022-2129/
ubuntu low CVE-2022-2129 low priority: Ubuntu including 1 source packages (vim), 8 status rows across 8 suites (bionic, focal, impish, jammy, kinetic, trusty, upstream, xenial): released 6, ignored 1, not-affected 1. https://ubuntu.com/security/CVE-2022-2129

Affected software / configurations for CVE-2022-2129

Vendor Product Version Raw CPE
vim vim < 8.2.5126 cpe:2.3:a:vim:vim:*:*:*:*:*:*:*:*
fedoraproject fedora 35 cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*
fedoraproject fedora 36 cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2022-2129

cvelogic Threat Intelligence