Is System.Security.Cryptography.X509Certificates 4.1 vulnerable?

NuGet · 3 releases from 4.1.0 to 4.1.2 · latest System.Security.Cryptography.X509Certificates is 4.3.2 · checked 18 Nov 2026

No known advisories in the last release

System.Security.Cryptography.X509Certificates 4.1.2, the last 4.1 release, has no known advisories. 1 advisory affects earlier 4.1.x releases, so update to 4.1.2.

Update within 4.1:dotnet add package System.Security.Cryptography.X509Certificates --version 4.1.2

Is your project on an affected System.Security.Cryptography.X509Certificates?

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 4.1.x, affecting earlier releases

  • HighCVE-2017-11770GHSA-7mfr-774f-w5r912 Apr 2022

    Improper Certificate Validation

    Affected
    >=4.0.0 <4.1.2
    Fixed in
    4.1.2

Every System.Security.Cryptography.X509Certificates 4.1.x release

Affected: 4.1.0 to 4.1.1. 4.1.2 is not affected. Latest System.Security.Cryptography.X509Certificates: 4.3.2.

VersionKnown advisories
System.Security.Cryptography.X509Certificates 4.1.2None
System.Security.Cryptography.X509Certificates 4.1.1CVE-2017-11770
System.Security.Cryptography.X509Certificates 4.1.0CVE-2017-11770

Which of your client projects are still on System.Security.Cryptography.X509Certificates 4.1?

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

Other System.Security.Cryptography.X509Certificates 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.