Vulnerability in CoreWCF.NetFramingBase (CVE-2026-54772)
Summary
Vulnerability in CoreWCF.NetFramingBase (CVE-2026-54772). 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
An unauthenticated remote attacker can pin one server thread‑pool worker at 100 % CPU per connection. With a few connections, the CPU usage can be exhausted.
Preconditions
An attacker being able to reach a service which is exposing an endpoint using one of NetTcpBinding, NetNamedPipeBinding, or UnixDomainSocketBinding.
Patches
Fixed in CoreWCF v1.8.1 and v1.9.1
Workarounds
None
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-54772 has been found in CoreWCF.NetFramingBase.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade CoreWCF.NetFramingBase to 1.9.1 or later.
If unsure, ask your IT team or search "CoreWCF.NetFramingBase CVE-2026-54772" on the vendor's site.
CVE-2026-54772 (CoreWCF.NetFramingBase) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / 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-400) exists in CoreWCF.NetFramingBase.
Check the vendor advisory for the affected versions of CoreWCF.NetFramingBase.
Severity: High (CVSS 7.5/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.NetFramingBase' . 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.NetFramingBase' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
CoreWCF.NetFramingBaseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade CoreWCF.NetFramingBase to 1.9.1ステージング環境で 1.9.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。