Vulnerability in CoreWCF.Kafka (CVE-2026-54775)
Summary
Vulnerability in CoreWCF.Kafka (CVE-2026-54775). 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, a CoreWCF service listening on a Kafka topic stops processing new records from that topic when KafkaTransportPump receives a null-value tombstone record, causing a persistent endpoint denial of service for attackers with produce permission. 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-54775 has been found in CoreWCF.Kafka.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade CoreWCF.Kafka to 1.9.1 or later.
If unsure, ask your IT team or search "CoreWCF.Kafka CVE-2026-54775" on the vendor's site.
CVE-2026-54775 (CoreWCF.Kafka) — CWE-248 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.9.1 — apply immediately
Workaround: Only allow authenticated writes to a topic
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-248) exists in CoreWCF.Kafka.
Check the vendor advisory for the affected versions of CoreWCF.Kafka.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.9.1.
Workaround: Only allow authenticated writes to a topic
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'CoreWCF.Kafka' . 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.Kafka' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
CoreWCF.Kafkaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Only allow authenticated writes to a topicパッチが適用されるまでの応急処置として、Only allow authenticated writes to a topic を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade CoreWCF.Kafka 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