Vulnerability in CoreWCF.UnixDomainSocket (CVE-2026-54776)
Summary
Vulnerability in CoreWCF.UnixDomainSocket (CVE-2026-54776). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.9.1 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54776 has been found in CoreWCF.UnixDomainSocket.
Risk of unauthorized operations or information disclosure. CVSS score: 4.4/10.
What to do: upgrade CoreWCF.UnixDomainSocket to 1.9.1 or later.
If unsure, ask your IT team or search "CoreWCF.UnixDomainSocket CVE-2026-54776" on the vendor's site.
CVE-2026-54776 (CoreWCF.UnixDomainSocket) — CWE-306 / CVSS v3 4.4
Attack vector: local / no user interaction
Patched: 1.9.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-306) exists in CoreWCF.UnixDomainSocket.
Check the vendor advisory for the affected versions of CoreWCF.UnixDomainSocket.
Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure.
Update to 1.9.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'CoreWCF.UnixDomainSocket' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'CoreWCF.UnixDomainSocket' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
CoreWCF.UnixDomainSocketを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade CoreWCF.UnixDomainSocket to 1.9.1ステージング環境で 1.9.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。