Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

NuGet package

corewcf.netnamedpipe

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5NuGetPublished

    CoreWCF NetNamedPipe transport accepts attach to a pre-existing named pipe instance

    CVE-2026-54777 · GHSA-6jj2-4q5c-x8g6

    Affected
    • NuGet corewcf.netnamedpipe < 1.8.1; >= 1.9.0, < 1.9.1
    Fixed in
    1.8.11.9.1· Vendor fix available
    Issue
    Impact CoreWCF NetNamedPipe transport accepts attach to a pre-existing named pipe instance, allowing local interception of NetNamedPipe traffic. NetNamedPipe creates a shared memory object based on the listening url, then generated a unique GUID for the named pipe it will be using and saves this to the shared memory object. Then it creates the named pipe to listen for clients. This requires an attacker to race the service and create the named pipe between the service publishing the GUID to the shared memory location (which the attacker needs to read) and the service creating the named pipe itself. Patches Fixed in CoreWCF v1.8.1 and v1.9.1 Workarounds None

    Recommended action: Upgrade to 1.9.1 or 1.8.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →