Skip to content
Fencer Vulns
low 2.8

CVE-2025-1215 json

vim main.c memory corruption

published 2025-02-12 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-2085

cvss
2.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

A vulnerability classified as problematic was found in vim up to 9.1.1096. This vulnerability affects unknown code of the file src/main.c. The manipulation of the argument --log leads to memory corruption. It is possible to launch the attack on the local host. Upgrading to version 9.1.1097 is able to address this issue. The patch is identified as c5654b84480822817bb7b69ebc97c174c91185e9. It is recommended to upgrade the affected component.

Patch / fix

  • vim vim 9.1.1097
  • vim Debian 14, Debian 13 2:9.1.1113-1

debian advisories DEBIAN-CVE-2025-1215

  • vim Ubuntu 24.04 LTS 2:9.1.0016-1ubuntu7.8

ubuntu advisories UBUNTU-CVE-2025-1215

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • vim SLE Micro 5.4, SLE Micro 5.3, SLE Micro 5.2 +1 more 9.1.1101-150000.5.69.1
  • vim SLE Module for Desktop Applications 15 SP6, SLE Module for Basesystem 15 SP6, SLE Micro 5.5 +1 more 9.1.1101-150500.20.21.1
  • vim Linux Micro 6.0 9.1.1101-1.1
  • vim SLES LTSS Extended Security 12 SP5 9.1.1101-17.41.1

suse advisories SUSE-SU-2025:0724-1SUSE-SU-2025:0723-1SUSE-SU-2025:0722-1SUSE-SU-2025:20128-1

  • vim CBL-Mariner 2.0, Azure Linux 3.0 9.1.0791-4

azure linux advisories AZL-56708AZL-56770

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-1215 updated cvss 2.8

vim: vim main.c memory corruption

  • Red Hat Enterprise Linux 6 vim, vim-X11, vim-common, vim-minimal, vim-enhanced, vim-filesystem Red Hat Enterprise Linux 7 vim, vim-X11, vim-common, vim-minimal, vim-enhanced, vim-filesystem Red Hat Enterprise Linux 8 vim, vim-X11, vim-common, vim-minimal, vim-enhanced, vim-filesystem
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 9 vim, vim-X11, vim-common, vim-minimal, vim-enhanced, vim-filesystem Red Hat Enterprise Linux 10 vim Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9
    affected: no fix available “Fix deferred”
  • Red Hat OpenShift AI (RHOAI) rhoai/odh-dashboard-rhel9
    under investigation

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
20 mo ago

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • vuldb.com https://vuldb.com/?submit.497546 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/vim/vim/issues/16606 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 2.4 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
CNA 3.1 2.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
CNA 3.0 2.8 CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
CNA 2.0 1.7 AV:L/AC:L/Au:S/C:N/I:N/A:P
CNA 4.0 2.4 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/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 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • n/a vim

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.