CVE-2001-0409: vim (aka gvim) allows local users to modify files being edited by other users via a symlink attack on the back

Routine

LOW 2.1DOWNGRADE

CVE-2001-0409 is a low-severity flaw (CVSS 2.1) affecting vim. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

vim (aka gvim) allows local users to modify files being edited by other users via a symlink attack on the backup and swap files, when the victim is editing the file in a world writable directory.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	2.1 (Low)
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Published	2001-06-18
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: vim development group

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2001-06-18 04:00 UTCPublished CVE record published
2026-06-16 21:54 UTCUpdated Record last modified

vim development group vim DOWNGRADE

Affected: 5.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.7

1. Check installed version

apt-cache policy vim || rpm -q vim || vim --version

2. No fixed release: DOWNGRADE to a release before 5.7 (Debian / Ubuntu)

apt-cache madison vim sudo apt install vim=<VERSION_BEFORE_5.7> sudo apt-mark hold vim

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list vim sudo dnf downgrade vim-<VERSION_BEFORE_5.7> sudo dnf versionlock add vim

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Vim 5.x - Swap File Race Condition

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2001-0409?

vim: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2001-0409 being exploited?

CVE-2001-0409 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2001-0409 affect?

CVE-2001-0409 affects vim. Severity is low (CVSS 2.1). vim (aka gvim) allows local users to modify files being edited by other users via a symlink attack on the backup and swap files, when the victim is editing the file in a world writable directory.

How urgent is CVE-2001-0409?

Priority 26/100. Public exploit reference

Software pages

Vim vulnerabilities

Related CVEs

CVE-2022-3235 HIGH 7.8 UPGRADE MITIGATE Use After Free in GitHub repository vim/vim prior to 9.0.0490.
CVE-2022-3234 HIGH 7.8 UPGRADE MITIGATE Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0483.
CVE-2022-3153 MEDIUM 5.5 UPGRADE NULL Pointer Dereference in GitHub repository vim/vim prior to 9.0.0404.
CVE-2022-3134 HIGH 7.8 UPGRADE UPGRADE Use After Free in GitHub repository vim/vim prior to 9.0.0389.
CVE-2022-3099 HIGH 7.8 UPGRADE MITIGATE Use After Free in GitHub repository vim/vim prior to 9.0.0360.

References

← Back to latest CVEs