Skip to content

← Public intelligence

NuGet package

corewcf.unixdomainsocket

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

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

  1. Medium, CVSS 6.2NuGetPublished

    CoreWCF: UnixDomainSocket Non-Reentrant POSIX Identity Resolution

    CVE-2026-54778 · GHSA-q6v9-43v5-jv9q

    Affected
    • NuGet corewcf.unixdomainsocket < 1.8.1; >= 1.9.0, < 1.9.1
    Fixed in
    1.8.11.9.1· Vendor fix available
    Issue
    Impact Race condition in POSIX peer identity resolution may attribute one connection’s identity to another (getpwuid/getgrgid non-reentrant) and may crash the host process under contention. Patches Fixed in CoreWCF v1.8.1 and v1.9.1 Workarounds Restrict UDS filesystem permissions so that only trusted local users can connect to the socket path. The race still exists but the attacker pool is constrained.

    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 →
  2. Medium, CVSS 4.4NuGetPublished

    CoreWCF: Unix Domain Socket PosixIdentity transport accepts connections that skip the security upgrade

    CVE-2026-54776 · GHSA-wjpq-6766-7f5j

    Affected
    • NuGet corewcf.unixdomainsocket < 1.8.1; >= 1.9.0, < 1.9.1
    Fixed in
    1.8.11.9.1· Vendor fix available
    Issue
    Impact A CoreWCF service hosted on Unix Domain Sockets with the PosixIdentity client credential type (UnixDomainSocketBinding with Security.Mode = TransportCredentialOnly and Security.Transport.ClientCredentialType = PosixIdentity) does not require the client to perform the application/unixposix stream upgrade before dispatching messages. Patches Fixed in CoreWCF v1.8.1 and v1.9.1 Workarounds Restrict filesystem access to the UDS socket file using owner/group/mode (e.g. chmod 0660 plus a dedicated group) so that only the POSIX users who are already authorized to invoke the service can connect at all. This makes the missing-upgrade behaviour equivalent to the operating system’s filesystem permissions instead of relying on framing-layer identity checks. Avoid relying on ServiceSecurityContext.PrimaryIdentity for authorization decisions, or back it up with an authentication-required authorization policy that rejects anonymous principals.

    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 →