CoreWCF.NetFramingBase vulnerabilities

CoreWCF is a port of the service side of Windows Communication Foundation (WCF) to .NET Core. The goal of this project is to enable existing WCF services to move to .NET Core.

Registry
NuGet
Latest
1.9.1
License
MIT

2 known advisories

The latest version, 1.9.1, is not affected by any of them. Projects on older versions may be.

Update to the latest version: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

Security advisories for CoreWCF.NetFramingBase

  • 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
  • HighCVE-2024-28252GHSA-32jq-mv89-5rx715 Mar 2024

    CoreWCF NetFraming based services can leave connections open when they should be closed

    Affected
    >=1.4.0 <1.4.2 · >=1.5.0 <1.5.2
    Fixed in
    1.4.2, 1.5.2

Is your CoreWCF.NetFramingBase version vulnerable?

Which of your client projects still run an old CoreWCF.NetFramingBase?

NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other NuGet packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.