https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 16:12:01 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-07097 bdu:2024-07097 https://cve.radiocsirt.org/vuln/bdu:2024-07097 https://cve.radiocsirt.org/vuln/bell-cve-2024-43374 <p><strong>Affected:</strong> Alpaquita:23: vim, Alpaquita:stream: vim</p> <p><strong>Affected:</strong> Alpaquita:23: vim, Alpaquita:stream: vim</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-43374 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0585 certfr-2025-avi-0585 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0585 https://cve.radiocsirt.org/vuln/cnvd-2024-40461 cnvd-2024-40461 https://cve.radiocsirt.org/vuln/cnvd-2024-40461 https://cve.radiocsirt.org/vuln/euvd-2026-186958 EUVD-2026-186958 https://cve.radiocsirt.org/vuln/euvd-2026-186958 https://cve.radiocsirt.org/vuln/fkie_cve-2024-43374 <p>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 a buffer during creation (either manually or by sourcing a malicious plugin), but it will crash Vim. The issue has been fixed as of Vim patch v9.1.0678.</p> <p>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 a buffer during creation (either manually or by sourcing a malicious plugin), but it will crash Vim. The issue has been fixed as of Vim patch v9.1.0678.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-43374 https://cve.radiocsirt.org/vuln/msrc_cve-2024-43374 msrc_CVE-2024-43374 https://cve.radiocsirt.org/vuln/msrc_cve-2024-43374 https://cve.radiocsirt.org/vuln/oesa-2024-2026 <p><strong>Affected:</strong> openEuler:22.03-LTS-SP1: vim, openEuler:24.03-LTS: vim, openEuler:22.03-LTS-SP4: vim, openEuler:22.03-LTS-SP3: vim, openEuler:20.03-LTS-SP4: vim</p> <p>Vim is an advanced text editor that seeks to provide the power of the de-facto Unix editor &amp;apos;Vi&amp;apos;, with a more complete feature set. Vim is a highly configurable text editor built to enable efficient text editing. It is an improved version of the vi editor distributed with most UNIX systems.</p> <p>Security Fix(es):</p> <p>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 a buffer during creation (either manually or by sourcing a malicious plugin), but it will crash Vim. The issue has been fixed as of Vim patch v9.1.0678.(CVE-2024-43374)</p> <p><strong>Affected:</strong> openEuler:22.03-LTS-SP1: vim, openEuler:24.03-LTS: vim, openEuler:22.03-LTS-SP4: vim, openEuler:22.03-LTS-SP3: vim, openEuler:20.03-LTS-SP4: vim</p> <p>Vim is an advanced text editor that seeks to provide the power of the de-facto Unix editor &amp;apos;Vi&amp;apos;, with a more complete feature set. Vim is a highly configurable text editor built to enable efficient text editing. It is an improved version of the vi editor distributed with most UNIX systems.</p> <p>Security Fix(es):</p> <p>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 a buffer during creation (either manually or by sourcing a malicious plugin), but it will crash Vim. The issue has been fixed as of Vim patch v9.1.0678.(CVE-2024-43374)</p> https://cve.radiocsirt.org/vuln/oesa-2024-2026 https://cve.radiocsirt.org/vuln/suse-su-2024:4330-1 <p>Security update for vim</p> <p>Security update for vim</p> https://cve.radiocsirt.org/vuln/suse-su-2024:4330-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-43374 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: vim, Ubuntu:Pro:16.04:LTS: vim, Ubuntu:Pro:18.04:LTS: vim, Ubuntu:20.04:LTS: vim, Ubuntu:22.04:LTS: vim, Ubuntu:24.04:LTS: vim</p> <p>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 a buffer during creation (either manually or by sourcing a malicious plugin), but it will crash Vim. The issue has been fixed as of Vim patch v9.1.0678.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: vim, Ubuntu:Pro:16.04:LTS: vim, Ubuntu:Pro:18.04:LTS: vim, Ubuntu:20.04:LTS: vim, Ubuntu:22.04:LTS: vim, Ubuntu:24.04:LTS: vim</p> <p>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 a buffer during creation (either manually or by sourcing a malicious plugin), but it will crash Vim. The issue has been fixed as of Vim patch v9.1.0678.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-43374 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1870 <p>Ein lokaler Angreifer kann eine Schwachstelle in vim ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann eine Schwachstelle in vim ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1870