Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2025-22134: heap-buffer-overflow with visual mode in Vim < 9.1.1003

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: azl3 vim 9.1.0791-2 on Azure Linux 3.0 9.1.0791-2; azl3 vim 9.1.0791-4 on Azure Linux 3.0 9.1.0791-2; cbl2 vim 9.1.0791-2 on CBL Mariner 2.0 9.1.0791-2.

Low priority for now. Upgrade to azl3 vim 9.1.0791-2 on Azure Linux 3.0 9.1.0791-2; azl3 vim 9.1.0791-4 on Azure Linux 3.0 9.1.0791-2; cbl2 vim 9.1.0791-2 on CBL Mariner 2.0 9.1.0791-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

When switching to other buffers using the :all command and visual mode still being active, this may cause a heap-buffer overflow, because Vim does not properly end visual mode and therefore may try to access beyond the end of a line in a buffer. In Patch 9.1.1003 Vim will correctly reset the visual mode before opening other windows and buffers and therefore fix this bug. In addition it does verify that it won't try to access a position if the position is greater than the corresponding buffer line. Impact is medium since the user must have switched on visual mode when executing the :all ex command. The Vim project would like to thank github user gandalf4a for reporting this issue. The issue has been fixed as of Vim patch v9.1.1003

Published
Jan 13, 2025
Updated
Jun 17, 2026
EPSS
0.3% · 31th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · GitHub_M
4.2
1.3 point gap

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-22134

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for neovim records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
neovimneovim
vimvim
netappbootstrap os
netapphci compute node

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • vim vim

    • < v9.1.1003affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • neovim neovimup to 0.10.4 inclusive
  • netapp bootstrap osall versions
  • vim vimup to 9.1.1003 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.21vimbefore 9.1.1003-r09.1.1003-r0
Debian:12vimfrom 0—
Debian:13vimbefore 2:9.1.1113-12:9.1.1113-1
openSUSE:Leap 15.6vimbefore 9.1.1101-150500.20.21.19.1.1101-150500.20.21.1
SUSE:Linux Enterprise Micro 5.3vimbefore 9.1.1101-150000.5.69.19.1.1101-150000.5.69.1
SUSE:Linux Enterprise Micro 5.5vimbefore 9.1.1101-150500.20.21.19.1.1101-150500.20.21.1
SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5vimbefore 9.1.1101-17.41.19.1.1101-17.41.1
SUSE:Linux Micro 6.0vimbefore 9.1.1101-1.19.1.1101-1.1

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 vim 9.1.0791-2 on Azure Linux 3.09.1.0791-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 vim 9.1.0791-4 on Azure Linux 3.09.1.0791-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 vim 9.1.0791-2 on CBL Mariner 2.09.1.0791-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 vim 9.1.0791-4 on CBL Mariner 2.09.1.0791-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 vim 9.1.0791-4 on CBL-Mariner 2.09.1.0791-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
alpine:vim9.1.1003-r0 · Alpine:v3.21Package registry (OSV)
debian:vim2:9.1.1113-1 · Debian:13Package registry (OSV)
opensuse:vim9.1.1101-150500.20.21.1 · openSUSE:Leap 15.6Package registry (OSV)
suse:vim9.1.1101-150500.20.21.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:vim9.1.1101-17.41.1 · SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-122 · Heap-based Buffer Overflow

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records