Vulnerability in CoreWCF.UnixDomainSocket (CVE-2026-54778)
Summary
Vulnerability in CoreWCF.UnixDomainSocket (CVE-2026-54778). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.9.1 or later.
Original description
The description as published by the source.
CoreWCF is a port of the service side of Windows Communication Foundation (WCF) to .NET Core. Prior to 1.8.1 and 1.9.1, CoreWCF UnixDomainSocket POSIX peer identity resolution uses non-reentrant getpwuid and getgrgid calls, allowing concurrent connections to attribute one connection's identity to another or crash the host process under contention. This issue is fixed in versions 1.8.1 and 1.9.1.
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-54778 has been found in CoreWCF.UnixDomainSocket.
Risk of unauthorized operations or information disclosure. CVSS score: 6.2/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-54778" on the vendor's site.
CVE-2026-54778 (CoreWCF.UnixDomainSocket) — CWE-362 / CVSS v3 6.2
Attack vector: local / unauthenticated / no user interaction
Patched: 1.9.1 — apply immediately
Workaround: Restrict UDS filesystem permissions so that only trusted local users can connect to the socket path.
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-362) exists in CoreWCF.UnixDomainSocket.
Check the vendor advisory for the affected versions of CoreWCF.UnixDomainSocket.
Severity: Medium (CVSS 6.2/10). Risk of unauthorized operations or information disclosure.
Update to 1.9.1.
Workaround: Restrict UDS filesystem permissions so that only trusted local users can connect to the socket path.
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 temporary workaround mitigate
Restrict UDS filesystem permissions so that only trusted local users can connect to the socket path.パッチが適用されるまでの応急処置として、Restrict UDS filesystem permissions so that only trusted local users can connect to the socket path. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade CoreWCF.UnixDomainSocket to 1.9.1ステージング環境で 1.9.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com