Vulnerability in CoreWCF.NetNamedPipe (CVE-2026-54777)
Summary
Vulnerability in CoreWCF.NetNamedPipe (CVE-2026-54777). Confidential information can be exposed externally. 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 NetNamedPipe transport accepts attachment to a pre-existing named pipe instance, allowing local interception of NetNamedPipe traffic when an attacker races NamedPipeListener startup between shared memory GUID publication and service named pipe creation. 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-54777 has been found in CoreWCF.NetNamedPipe.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade CoreWCF.NetNamedPipe to 1.9.1 or later.
If unsure, ask your IT team or search "CoreWCF.NetNamedPipe CVE-2026-54777" on the vendor's site.
CVE-2026-54777 (CoreWCF.NetNamedPipe) — CWE-367 / CVSS v3 6.5
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-367) exists in CoreWCF.NetNamedPipe.
Check the vendor advisory for the affected versions of CoreWCF.NetNamedPipe.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
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.NetNamedPipe' . 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.NetNamedPipe' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
CoreWCF.NetNamedPipeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade CoreWCF.NetNamedPipe to 1.9.1ステージング環境で 1.9.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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
- web github.com
- web github.com
- web github.com