CVE-2022-3037: Use After Free in GitHub repository vim/vim prior to 9.0.0322.

Q: How do I fix CVE-2022-3037?

neovim: upgrade to 0.9.0; vim: upgrade to 9.0.0322; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2022-3037 being exploited?

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

Q: What does CVE-2022-3037 affect?

CVE-2022-3037 affects neovim, vim, fedora. Severity is high (CVSS 7.8). Use After Free in GitHub repository vim/vim prior to 9.0.0322.

Q: How urgent is CVE-2022-3037?

Priority 44/100. High severity; Public exploit reference

This month

HIGH 7.8UPGRADEUPGRADEMITIGATE

CVE-2022-3037 is a high-severity flaw (CVSS 7.8) affecting neovim, vim, fedora. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Use After Free in GitHub repository vim/vim prior to 9.0.0322.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.5% (top 55%)
CISA exploited list	No
Weakness	CWE-416
Published	2022-08-30
Last modified	2026-11-02

Publisher (CNA): huntr.dev · Vendor: fedoraproject · neovim · vim

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

Am I affected?

Timeline

2022-08-30 21:15 UTCPublished CVE record published
2026-11-02 22:17 UTCUpdated Record last modified

neovim neovim UPGRADE

Affected: >= 0.5.0 and < 0.9.0

Fixed in: 0.9.0

Safe to downgrade to: a release before 0.5.0

1. Check installed version

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

2. UPGRADE to 0.9.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade neovim

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade neovim

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 0.5.0 (Debian / Ubuntu)

apt-cache madison neovim sudo apt install neovim=<VERSION_BEFORE_0.5.0> sudo apt-mark hold neovim

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list neovim sudo dnf downgrade neovim-<VERSION_BEFORE_0.5.0> sudo dnf versionlock add neovim

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.

vim vim UPGRADE

Affected: < 9.0.0322

Fixed in: 9.0.0322

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 9.0.0322 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vim

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vim

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

fedoraproject fedora MITIGATE

Affected: 35 · 36 · 37

Fixed in: no fixed release known

Safe to downgrade to: a release before 35

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

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-2022-3037?

neovim: upgrade to 0.9.0; vim: upgrade to 9.0.0322; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-3037 being exploited?

CVE-2022-3037 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-2022-3037 affect?

CVE-2022-3037 affects neovim, vim, fedora. Severity is high (CVSS 7.8). Use After Free in GitHub repository vim/vim prior to 9.0.0322.

How urgent is CVE-2022-3037?

Priority 44/100. High severity; Public exploit reference

Software pages

GitHub vulnerabilities · Vim vulnerabilities

Related CVEs

CVE-2022-3134 HIGH 7.8 UPGRADE UPGRADE Use After Free in GitHub repository vim/vim prior to 9.0.0389.
CVE-2023-0433 HIGH 7.8 UPGRADE MITIGATE Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.1225.
CVE-2022-3256 HIGH 7.8 UPGRADE UPGRADE Use After Free in GitHub repository vim/vim prior to 9.0.0530.
CVE-2023-0288 HIGH 7.8 UPGRADE MITIGATE Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.1189.
CVE-2022-3296 HIGH 7.8 UPGRADE UPGRADE Stack-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0577.

References

← Back to latest CVEs