Is CoreWCF.NetFramingBase 1.7 vulnerable?

NuGet · 1 release from 1.7.0 to 1.7.0 · latest CoreWCF.NetFramingBase is 1.9.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. CoreWCF.NetFramingBase 1.7.0, the last 1.7 release, is affected by 1 known security advisory (1 high), including CVE-2026-54772. Upgrade to 1.8.1 or later to fix all of them.

Upgrade with:dotnet add package CoreWCF.NetFramingBase --version 1.8.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

Advisories affecting CoreWCF.NetFramingBase 1.7.0

  • 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

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

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.