Home/CVE/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,
CVE
CVE-2026-54775
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 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.
MEDIUM · CVSS 6.5
Monitor
- No active-exploitation, high-EPSS, or public-exploit signals - routine patching cadence
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-54775, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
EPSS exploitation probability
n/a
No EPSS score in our data for this CVE. EPSS is published daily for scored CVEs - a very new, reserved, or rejected CVE may not have one yet.
CVSS metric silhouette
shape grows toward worst-case
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H◆
ATT&CK techniques
1Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.
▤ Build a SIEM detection for these techniques⬡
Weakness Classification
▤
Affected Packages
1Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
NuGet
CoreWCF.Kafka
MODERATE
fixed in 1.8.1
▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-2013-10065
A denial-of-service vulnerability exists in Sysax Multi-Server version 6.10 via...
same CWE-248
HIGH
CVE-2016-10363
Logstash versions prior to 2.3.3, when using the Netflow Codec plugin, a remote ...
same CWE-248
HIGH
CVE-2018-11464
A vulnerability has been identified in SINUMERIK 828D V4.7 (All versions < V4.7 ...
same CWE-248
LOW
CVE-2018-11465
A vulnerability has been identified in SINUMERIK 808D V4.7 (All versions), SINUM...
same CWE-248
HIGH
CVE-2014-1737
The raw_cmd_copyin function in drivers/block/floppy.c in the Linux kernel throug...
same CWE-754
CVE-2016-8209
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00...
same CWE-754
HIGH
CVE-2017-0610
An elevation of privilege vulnerability in the Qualcomm sound driver could enabl...
same CWE-754
HIGH
CVE-2017-11144
In PHP before 5.6.31, 7.x before 7.0.21, and 7.1.x before 7.1.7, the openssl ext...
same CWE-754
HIGH
🔗
References & Sources
6Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.