Is i18n 2.1 vulnerable?

NuGet · 14 releases from 2.1.0 to 2.1.17 · latest i18n is 2.1.17 · checked 18 Nov 2026

No known advisories in the last release

i18n 2.1.17, the last 2.1 release, has no known advisories. 1 advisory affects earlier 2.1.x releases, so update to 2.1.17.

Update within 2.1:dotnet add package i18n --version 2.1.17

Is your project on an affected i18n?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 2.1.x, affecting earlier releases

  • HighCVE-2020-7791GHSA-hfvc-g252-rp4g14 Dec 2020

    Denial of Service in i18n

    Affected
    <2.1.15
    Fixed in
    2.1.15

Every i18n 2.1.x release

Affected: 2.1.0 to 2.1.14. 2.1.15 and later are not affected.

VersionKnown advisories
i18n 2.1.17None
i18n 2.1.16None
i18n 2.1.15None
i18n 2.1.14CVE-2020-7791
i18n 2.1.11CVE-2020-7791
i18n 2.1.10CVE-2020-7791
i18n 2.1.8CVE-2020-7791
i18n 2.1.7CVE-2020-7791
i18n 2.1.6CVE-2020-7791
i18n 2.1.5CVE-2020-7791
i18n 2.1.4CVE-2020-7791
i18n 2.1.3CVE-2020-7791
i18n 2.1.1CVE-2020-7791
i18n 2.1.0CVE-2020-7791

Which of your client projects are still on i18n 2.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact i18n version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other i18n versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.