CVE-2001-0408: vim (aka gvim) processes VIM control codes that are embedded in a file, which could allow attackers to execute

Routine

MEDIUM 5.1DOWNGRADE

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

vim (aka gvim) processes VIM control codes that are embedded in a file, which could allow attackers to execute arbitrary commands when another user opens a file containing malicious VIM control codes.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	5.1 (Medium)
EPSS exploit chance	1.7% (top 23%)
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.

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-0408?

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

Is CVE-2001-0408 being exploited?

CVE-2001-0408 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-0408 affect?

CVE-2001-0408 affects vim. Severity is medium (CVSS 5.1). vim (aka gvim) processes VIM control codes that are embedded in a file, which could allow attackers to execute arbitrary commands when another user opens a file containing malicious VIM control codes.

How urgent is CVE-2001-0408?

Priority 37/100. No elevated risk signals yet.

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