Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2025-26603: heap-use-after-free in function str_to_reg in vim/vim

MediumCVSS 4.2 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 16/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.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
  • Fixed version: azl3 vim 9.1.0791-4 on Azure Linux 3.0 9.1.0791-4; cbl2 vim 9.1.0791-4 on CBL Mariner 2.0 9.1.0791-4; cbl2 vim 9.1.0791-4 on CBL-Mariner 2.0 9.1.0791-4.

Low priority for now. Upgrade to azl3 vim 9.1.0791-4 on Azure Linux 3.0 9.1.0791-4; cbl2 vim 9.1.0791-4 on CBL Mariner 2.0 9.1.0791-4; cbl2 vim 9.1.0791-4 on CBL-Mariner 2.0 9.1.0791-4 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

Vim is a greatly improved version of the good old UNIX editor Vi. Vim allows to redirect screen messages using the `:redir` ex command to register, variables and files. It also allows to show the contents of registers using the `:registers` or `:display` ex command. When redirecting the output of `:display` to a register, Vim will free the register content before storing the new content in the register. Now when redirecting the `:display` command to a register that is being displayed, Vim will free the content while shortly afterwards trying to access it, which leads to a use-after-free. Vim pre 9.1.1115 checks in the ex_display() function, that it does not try to redirect to a register while displaying this register at the same time. However this check is not complete, and so Vim does not check the `+` and `*` registers (which typically donate the X11/clipboard registers, and when a clipboard connection is not possible will fall back to use register 0 instead. In Patch 9.1.1115 Vim will therefore skip outputting to register zero when trying to redirect to the clipboard registers `*` or `+`. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Published
Feb 18, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile

Report tools

JSON

Action score

16

Monitor

Low priority for now.

CVSS
16 / 40 · 4.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
4.2
NVD has not scored this yet; the score shown is the CNA’s.

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-26603

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
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
vimvim
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

    • < 9.1.1115affected

Affected versions

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

  • netapp hci compute nodeall versions
  • vim vimbefore 9.1.1115

Package-level exposure

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

EcosystemPackageAffected rangeFix
Alpine:v3.22vimbefore 9.1.1164-r09.1.1164-r0
Debian:12vimfrom 0—
Debian:13vimbefore 2:9.1.1230-12:9.1.1230-1

Same product

vim: all records

Other highest-scoring records for the same primary product.

  • CVE-2008-2712Vim 7.1.314, 6.4, and other versions allows user-assisted remote attackers to execute arbitrary commands via Vim scripts that do not…
    42Plan
  • CVE-2022-0318Heap-based Buffer Overflow in vim/vim
    40Plan
  • CVE-2019-12735getchar.c in Vim before 8.1.1365 and Neovim before 0.3.6 allows remote attackers to execute arbitrary OS commands via the :source! command…
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-24014Jan 20, 2025 · segmentation fault in win_line() in Vim < 9.1.1043
    22Monitor
  • ← EarlierCVE-2025-1215Feb 12, 2025 · vim main.c memory corruption
    9Monitor
  • Later →CVE-2025-27423Mar 3, 2025 · Improper Input Validation in Vim
    35Monitor

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-4 on Azure Linux 3.09.1.0791-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 vim 9.1.0791-4 on CBL Mariner 2.09.1.0791-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 vim 9.1.0791-4 on CBL-Mariner 2.09.1.0791-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
alpine:vim9.1.1164-r0 · Alpine:v3.22Package registry (OSV)
debian:vim2:9.1.1230-1 · Debian:13Package 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.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-5535496 days apartUse After Free in vim/vim
    31Monitor
  • CVE-2023-4733533 days apartUse After Free in vim/vim
    31Monitor
  • CVE-2023-4750533 days apartUse After Free in vim/vim
    31Monitor
  • CVE-2023-4752533 days apartUse After Free in vim/vim
    31Monitor
  • CVE-2025-55157174 days apartVim heap use-after-free vulnerability when processing recursive tuple data types
    27Monitor
  • CVE-2024-47814134 days apartuse-after-free when closing buffers in Vim
    18Monitor

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

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
Low

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

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

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (2 more)

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

All records