CVE-2025-26603: heap-use-after-free in function str_to_reg in vim/vim
heap-use-after-free in function strtoreg in vim/vim
Other sources
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 exdisplay() 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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/vimto a version that resolves this vulnerability.Fixed in 2:9.1.1230-1 - Upgrade
Upgrade
Vimto a version that resolves this vulnerability.Fixed in 9.1.1115 - Compensating control
Since there are no known workarounds for this vulnerability, limit exposure by avoiding use of the Vim `:redir` command to redirect `:display` output to a register that is currently being displayed, until you can upgrade.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-26603?
CVE-2025-26603 has a medium severity rating due to its potential for unintended information disclosure.
How do I fix CVE-2025-26603?
To fix CVE-2025-26603, upgrade to Vim version 9.1.1116 or later where the vulnerability has been addressed.
What are the potential impacts of CVE-2025-26603?
The potential impacts of CVE-2025-26603 include unauthorized access to sensitive information stored in registers.
Is CVE-2025-26603 exploitable remotely?
CVE-2025-26603 is not considered exploitable remotely, as it requires local access to the Vim editor.
Which versions of Vim are affected by CVE-2025-26603?
CVE-2025-26603 affects Vim versions up to and including 9.1.1115.