Vulnerability Database · Debian · Package report

vim: vulnerability history, versions and safety

vim is a package in the Debian ecosystem. Vulert records 190 vulnerabilities for it across 63 releases, from Nov -0001 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
190 vulnerabilities recorded U190
i
104 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
37 in the last 12 months

Most recent disclosure 18 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on vim i

Updated on 23 Oct 2026

Careful: 104 of the 190 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 190 vulnerabilities on record across 2026 years, 37 in the last year.

What to do: Plan around the 104 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 190 over 2026 years · 37 in the last year i
  • Latest disclosure 18 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 104 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for vim, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2:9.2.0858-1 U7 No Details →
2:9.2.0782-1 U10 No Details →
2:9.2.0524-1 U23 No Details →
2:9.2.0461-1 U25 No Details →
2:9.2.0428-1 U28 No Details →
2:9.2.0355-1 U29 No Details →
2:9.2.0338-1 U29 No Details →
2:9.2.0315-1 U30 No Details →
2:9.2.0218-1 U33 No Details →
2:9.2.0136-1 U34 No Details →
2:9.2.0119-1 U34 No Details →
2:9.1.2141-1 U41 No Details →
2:9.1.2103-1 U42 No Details →
2:9.1.1882-1 U42 No Details →
2:9.1.1846-1 U42 No Details →
2:9.1.1829-1 U42 No Details →
2:9.1.1766-1 U47 No Details →
2:9.1.1385-1 U104 No Details →
2:9.1.1230-2 U104 No Details →
2:9.1.1230-1 U104 No Details →
2:9.1.1113-1 U104 No Details →
2:9.1.0967-2 U104 No Details →
2:9.1.0967-1 U104 No Details →
2:9.1.0861-1 U104 No Details →
2:9.1.0777-1 U104 No Details →
2:9.1.0709-2 U104 No Details →
2:9.1.0709-1 U104 No Details →
2:9.1.0698-1 U104 No Details →
2:9.1.0496-1 U104 No Details →
2:9.1.0377-1 U104 No Details →
2:9.1.0374-1 U104 No Details →
2:9.1.0199-1 U104 No Details →
2:9.1.0016-1 U104 No Details →
2:9.1.0-1 U104 No Details →
2:9.0.2189-1 U104 No Details →
2:9.0.2116-1 U104 No Details →
2:9.0.2103-1 U104 No Details →
2:9.0.2087-1 U104 No Details →
2:9.0.2018-1 U104 No Details →
2:9.0.1894-1 U104 No Details →
2:9.0.1672-1 U104 No Details →
2:9.0.1658-1 U104 No Details →
2:9.0.1378-2 U104 No Details →
2:9.0.1378-1 U104 No Details →
2:9.0.1000-4 U104 No Details →
2:9.0.1000-3 U104 No Details →
2:9.0.1000-2 U104 No Details →
2:9.0.1000-1 U104 No Details →
2:9.0.0813-1 U104 No Details →
2:9.0.0626-1 U104 No Details →
2:9.0.0242-1 U104 No Details →
2:9.0.0229-1 U104 No Details →
2:9.0.0135-1 U104 No Details →
2:8.2.4793-1 U104 No Details →
2:8.2.4659-1 U104 No Details →
2:8.2.3995-1 U104 No Details →
2:8.2.3565-1 U104 No Details →
2:8.2.3455-2 U104 No Details →
2:8.2.3455-1 U104 No Details →
2:8.2.2434-3 U151 No Details →
2:8.2.2434-3+deb11u3 U104 No Details →
2:8.2.2434-3+deb11u2 U104 No Details →
2:8.2.2434-3+deb11u1 U148 No Details →

Newest 63 of 63 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 5
  • 2002 2
  • 2005 6
  • 2007 4
  • 2008 6
  • 2009 10
  • 2017 6
  • 2019 3
  • 2020 2
  • 2021 8
  • 2022 66
  • 2023 23
  • 2024 4
  • 2025 8
  • 2026 37

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 37 of the 190 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for vim

The 5 most severe of 190 vulnerabilities recorded for this package

Search all 190 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About vim

Is vim safe to use?

Vulert records 190 vulnerabilities for vim in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 190 not yet rated. 104 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does vim have?

190 vulnerabilities are recorded for vim in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 190 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new vim vulnerabilities disclosed?

37 vulnerabilities were recorded for vim in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of vim are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor vim for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the vim version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.