Is i18n 1.0 vulnerable?
NuGet · 8 releases from 1.0.0 to 1.0.8 · latest i18n is 2.1.17 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. i18n 1.0.8, the last 1.0 release, is affected by 1 known security advisory (1 high), including CVE-2020-7791. Upgrade to 2.1.15 or later to fix all of them.
dotnet add package i18n --version 2.1.15Is your project on an affected i18n?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting i18n 1.0.8
Denial of Service in i18n
- Affected
- <2.1.15
- Fixed in
- 2.1.15
Every i18n 1.0.x release
Affected: 1.0.0 to 1.0.8. Latest i18n: 2.1.17.
| Version | Known advisories |
|---|---|
| i18n 1.0.8 | CVE-2020-7791 |
| i18n 1.0.7 | CVE-2020-7791 |
| i18n 1.0.6 | CVE-2020-7791 |
| i18n 1.0.5 | CVE-2020-7791 |
| i18n 1.0.4 | CVE-2020-7791 |
| i18n 1.0.2 | CVE-2020-7791 |
| i18n 1.0.1 | CVE-2020-7791 |
| i18n 1.0.0 | CVE-2020-7791 |
Which of your client projects are still on i18n 1.0?
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.