Vim heap-use-after-free in src/arglist.c:207
Noroxi assessment
Priority: Monitor (action score 18/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.35% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Azure Linux 3.0 ARM 9.0.2190-5; Azure Linux 3.0 x64 9.0.2190-5; CBL Mariner 2.0 ARM 9.0.2121-3.
Low priority for now. Upgrade to Azure Linux 3.0 ARM 9.0.2190-5; Azure Linux 3.0 x64 9.0.2190-5; CBL Mariner 2.0 ARM 9.0.2121-3 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
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.
- Published
- Aug 15, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 27th percentile
- CWE
- CWE-416
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 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
- 4.7
- CNA · GitHub_M
- 4.5
- 0.2 point gap
CVSS:3.1/AV:L/AC:H/PR:N/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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| vim | vim | cpe:2.3:a:vim:vim |
| netapp | bootstrap os | cpe:2.3:o:netapp:bootstrap_os |
| netapp | hci compute node | cpe:2.3:h:netapp:hci_compute_node |
| neovim | neovim | cpe:2.3:a:neovim:neovim |
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 vimbefore 9.1.0678
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.0678affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.20 | vim | before 9.1.0678-r0 | 9.1.0678-r0 |
| Debian:12 | vim | from 0 | — |
| Debian:13 | vim | before 2:9.1.0698-1 | 2:9.1.0698-1 |
| openSUSE:Leap Micro 5.5 | vim | before 9.1.0836-150500.20.15.1 | 9.1.0836-150500.20.15.1 |
| SUSE:Linux Enterprise Micro 5.5 | vim | before 9.1.0836-150500.20.15.1 | 9.1.0836-150500.20.15.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | vim | before 9.1.0836-17.38.1 | 9.1.0836-17.38.1 |
| SUSE:Linux Micro 6.0 | vim | before 9.1.1101-1.1 | 9.1.1101-1.1 |
Same product
vim: all recordsOther 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 properl42Plan
- CVE-2022-0318Heap-based Buffer Overflow in vim/vim40Plan
- 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 i40Plan
Published before and after this one in the same product
- ← EarlierCVE-2024-41957Aug 1, 2024 · Vim double free in src/alloc.c:61621Monitor
- ← EarlierCVE-2024-41965Aug 1, 2024 · Vim < v9.1.0648 has a double-free in dialog_changed()16Monitor
- Later →CVE-2024-43790Aug 22, 2024 · heap-buffer-overflow in do_search() in Vim < 9.1.068922Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Azure Linux 3.0 ARM | 9.0.2190-5 · vim | Microsoft (MSRC) |
| Azure Linux 3.0 x64 | 9.0.2190-5 · vim | Microsoft (MSRC) |
| CBL Mariner 2.0 ARM | 9.0.2121-3 · vim | Microsoft (MSRC) |
| CBL Mariner 2.0 x64 | 9.0.2121-3 · vim | Microsoft (MSRC) |
| alpine:vim | 9.1.0678-r0 · Alpine:v3.20 | Package registry (OSV) |
| debian:vim | 2:9.1.0698-1 · Debian:13 | Package registry (OSV) |
| opensuse:vim | 9.1.0836-150500.20.15.1 · openSUSE:Leap Micro 5.5 | Package registry (OSV) |
| suse:vim | 9.1.0836-150500.20.15.1 · SUSE:Linux Enterprise Micro 5.5 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-5535309 days apartUse After Free in vim/vim31Monitor
- CVE-2023-4733346 days apartUse After Free in vim/vim31Monitor
- CVE-2023-4750346 days apartUse After Free in vim/vim31Monitor
- CVE-2023-4752346 days apartUse After Free in vim/vim31Monitor
- CVE-2025-55157361 days apartVim heap use-after-free vulnerability when processing recursive tuple data types27Monitor
- CVE-2024-4781453 days apartuse-after-free when closing buffers in Vim18Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.