# CVE-2026-26269: Vim has a Netbeans specialKeys Stack Buffer Overflow

> A stack buffer overflow in Vim's NetBeans integration allows a malicious server to execute arbitrary code via a crafted specialKeys command.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Feb 2026
- **Updated:** 13 Feb 2026
- **Also known as:** AZL-77592, AZL-77850, BELL-CVE-2026-26269, CLSA-2026-1772466351, CLSA-2026-1772622920, CLSA-2026-1772703383, CLSA-2026-1772703948, CLSA-2026-1772814085, CLSA-2026-1773141936, CLSA-2026-1773505564, CLSA-2026-1773506143, DEBIAN-CVE-2026-26269, ECHO-d50c-d5dc-4726, GHSA-9w5c-hwr9-hc68, MGASA-2026-0042, OESA-2026-1429, OESA-2026-1497, OESA-2026-1498, OESA-2026-1499, OESA-2026-1500, OESA-2026-1501, ROOT-OS-DEBIAN-12-CVE-2026-26269

## What is CVE-2026-26269?

CVE-2026-26269 is a medium-severity memory corruption vulnerability in Vim Vim, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vim is an open source, command line text editor. Prior to 9.1.2148, a stack buffer overflow vulnerability exists in Vim's NetBeans integration when processing the specialKeys command, affecting Vim builds that enable and use the NetBeans feature. The Stack buffer overflow exists in special_keys() (in src/netbeans.c). The while (*tok) loop writes two bytes per iteration into a 64-byte stack buffer (keybuf) with no bounds check. A malicious NetBeans server can overflow keybuf with a single specialKeys command. The issue has been fixed as of Vim patch v9.1.2148.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-26269?

It affects 1 product.


Products: Vim Vim.

## How do I fix CVE-2026-26269?

Apply the vendor's patch.

## Is CVE-2026-26269 being exploited?

There is no known exploitation of CVE-2026-26269 in the wild and no public exploit code.

## Other vulnerabilities in Vim Vim

- [CVE-2020-20703](https://insights.sbomify.com/CVE-2020-20703/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-6349](https://insights.sbomify.com/CVE-2017-6349/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-6350](https://insights.sbomify.com/CVE-2017-6350/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-5953](https://insights.sbomify.com/CVE-2017-5953/): Integer overflow in n/a (critical 9.8)
- [CVE-2008-3075](https://insights.sbomify.com/CVE-2008-3075/): Command injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26269 and fix it if it is affected.

What it is: CVE-2026-26269 is a medium-severity memory corruption vulnerability in Vim Vim, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-26269 in the wild and no public exploit code.

Affected product: Vim Vim. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26269/ (Markdown: https://insights.sbomify.com/CVE-2026-26269/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26269
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26269
- OSV: https://osv.dev/vulnerability/CVE-2026-26269

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26269/
Summaries are generated and may contain mistakes; the official description above is the record.