Is CoreWCF.NetFramingBase 1.9 vulnerable?

NuGet · 2 releases from 1.9.0 to 1.9.1 · latest CoreWCF.NetFramingBase is 1.9.1 · checked 18 Nov 2026

No known advisories in the last release

CoreWCF.NetFramingBase 1.9.1, the last 1.9 release, has no known advisories. 1 advisory affects earlier 1.9.x releases, so update to 1.9.1.

Update within 1.9:dotnet add package CoreWCF.NetFramingBase --version 1.9.1

Is your project on an affected CoreWCF.NetFramingBase?

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

  • HighCVE-2026-54772GHSA-p86g-xrr2-pf7c19 Jun 2026

    CoreWCF: Pre-authentication infinite-loop CPU exhaustion in CoreWCF net.tcp / net.pipe / net.uds framing handshake

    Affected
    <1.8.1 · >=1.9.0 <1.9.1
    Fixed in
    1.8.1, 1.9.1

Every CoreWCF.NetFramingBase 1.9.x release

Affected: 1.9.0. 1.9.1 is not affected.

VersionKnown advisories
CoreWCF.NetFramingBase 1.9.1None
CoreWCF.NetFramingBase 1.9.0CVE-2026-54772

Which of your client projects are still on CoreWCF.NetFramingBase 1.9?

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

Other CoreWCF.NetFramingBase 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.