p PatchFirst

PatchFirst · Latest vulnerabilities

vim vulnerabilities

Vulnerabilities published for vim in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 121

  1. CVE-2025-24014

    Medium · CVSS 4.2EPSS 0.28%Fix available

    segmentation fault in win_line() in Vim < 9.1.1043

    Vim is an open source, command line text editor. A segmentation fault was found in Vim before 9.1.1043. In silent Ex mode (-s -e), Vim typically doesn't show a screen and just operates silently in batch mode. However, it is still possible to trigger the function that handles the scrolling of a gui version of Vim by feeding some binary characters to Vim. The function that handles the scrolling however may be triggering a redraw, which will access the ScreenLines pointer, even so this variable hasn't been allocated (since there is no screen). This vulnerability is fixed in 9.1.1043.

    • Update to 9.1.1105-r0
    Published Updated
  2. CVE-2025-22134

    Medium · CVSS 4.2EPSS 0.38%Fix available

    heap-buffer-overflow with visual mode in Vim < 9.1.1003

    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 us

    • Update to 9.1.1003-r0
    Published Updated
  3. CVE-2024-47814

    Low · CVSS 3.9EPSS 0.3%Fix available

    use-after-free when closing buffers in Vim

    Vim is an open source, command line text editor. A use-after-free was found in Vim < 9.1.0764. When closing a buffer (visible in a window) a BufWinLeave auto command can cause an use-after-free if this auto command happens to re-open the same buffer in a new split window. Impact is low since the user must have intentionally set up such a strange auto command and run some buffer unload commands. However this may lead to a crash. This issue has been addressed in version 9.1.0764 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

    • Update to 9.1.0936-r0
    Published Updated
  4. CVE-2024-43802

    Medium · CVSS 4.5EPSS 0.3%Fix available

    heap-buffer-overflow in ins_typebuf() in Vim < 9.1.0697

    Vim is an improved version of the unix vi text editor. When flushing the typeahead buffer, Vim moves the current position in the typeahead buffer but does not check whether there is enough space left in the buffer to handle the next characters. So this may lead to the tb_off position within the typebuf variable to point outside of the valid buffer size, which can then later lead to a heap-buffer overflow in e.g. ins_typebuf(). Therefore, when flushing the typeahead buffer, check if there is enough space left before advancing the off position. If not, fall back to flush current typebuf contents. It's not quite clear yet, what can lead to this

    • Update to 9.1.0707-r0
    Published Updated
  5. CVE-2024-43790

    Medium · CVSS 4.5EPSS 0.31%Fix available

    heap-buffer-overflow in do_search() in Vim < 9.1.0689

    Vim is an open source command line text editor. When performing a search and displaying the search-count message is disabled (:set shm+=S), the search pattern is displayed at the bottom of the screen in a buffer (msgbuf). When right-left mode (:set rl) is enabled, the search pattern is reversed. This happens by allocating a new buffer. If the search pattern contains some ASCII NUL characters, the buffer allocated will be smaller than the original allocated buffer (because for allocating the reversed buffer, the strlen() function is called, which only counts until it notices an ASCII NUL byte ) and thus the original length indicator is wrong.

    • Update to 9.1.0707-r0
    Published Updated
  6. CVE-2024-43374

    Medium · CVSS 4.5EPSS 0.35%Fix available

    Vim heap-use-after-free in src/arglist.c:207

    The UNIX editor Vim prior to version 9.1.0678 has a use-after-free error in argument list handling. When adding a new file to the argument list, this triggers `Buf*` autocommands. If in such an autocommand the buffer that was just opened is closed (including the window where it is shown), this causes the window structure to be freed which contains a reference to the argument list that we are actually modifying. Once the autocommands are completed, the references to the window and argument list are no longer valid and as such cause an use-after-free. Impact is low since the user must either intentionally add some unusual autocommands that wipe

    • Update to 9.1.0678-r0
    Published Updated
  7. CVE-2024-41965

    Medium · CVSS 4.2EPSS 0.33%Fix available

    Vim < v9.1.0648 has a double-free in dialog_changed()

    Vim is an open source command line text editor. double-free in dialog_changed() in Vim < v9.1.0648. When abandoning a buffer, Vim may ask the user what to do with the modified buffer. If the user wants the changed buffer to be saved, Vim may create a new Untitled file, if the buffer did not have a name yet. However, when setting the buffer name to Unnamed, Vim will falsely free a pointer twice, leading to a double-free and possibly later to a heap-use-after-free, which can lead to a crash. The issue has been fixed as of Vim patch v9.1.0648.

    • Update to 9.1.0652-r0
    Published Updated
  8. CVE-2024-41957

    Medium · CVSS 4.5EPSS 0.37%Fix available

    Vim double free in src/alloc.c:616

    Vim is an open source command line text editor. Vim < v9.1.0647 has double free in src/alloc.c:616. When closing a window, the corresponding tagstack data will be cleared and freed. However a bit later, the quickfix list belonging to that window will also be cleared and if that quickfix list points to the same tagstack data, Vim will try to free it again, resulting in a double-free/use-after-free access exception. Impact is low since the user must intentionally execute vim with several non-default flags, but it may cause a crash of Vim. The issue has been fixed as of Vim patch v9.1.0647

    • Update to 9.1.0652-r0
    Published Updated
  9. CVE-2023-48706

    Low · CVSS 3.6EPSS 0.54%Fix available

    Vim has heap-use-after-free at /src/charset.c:1770:12 in skipwhite

    Vim is a UNIX editor that, prior to version 9.0.2121, has a heap-use-after-free vulnerability. When executing a `:s` command for the very first time and using a sub-replace-special atom inside the substitution part, it is possible that the recursive `:s` call causes free-ing of memory which may later then be accessed by the initial `:s` command. The user must intentionally execute the payload and the whole process is a bit tricky to do since it seems to work only reliably for the very first :s command. It may also cause a crash of Vim. Version 9.0.2121 contains a fix for this issue.

    • Update to 9.0.2127-r0
    Published Updated
  10. CVE-2023-48231

    Low · CVSS 3.9EPSS 0.71%Fix available

    Use-After-Free in win_close() in vim

    Vim is an open source command line text editor. When closing a window, vim may try to access already freed window structure. Exploitation beyond crashing the application has not been shown to be viable. This issue has been addressed in commit `25aabc2b` which has been included in release version 9.0.2106. Users are advised to upgrade. There are no known workarounds for this vulnerability.

    • Update to 9.0.2112-r0
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →