Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
CoreWCF.NetFramingBase versions 1.4.0 before 1.4.2 and 1.5.0 before 1.5.2 can leave connections open when they should be closed, consuming extra system resources. A client that connects and sends no data, or a session that goes idle past the binding ReceiveTimeout, can keep its connection established; the flaw affects NetTcpBinding, NetNamedPipeBinding, and UnixDomainSocketBinding, with only NetTcpBinding accepting non-local connections. Upgrade to CoreWCF.NetFramingBase 1.4.2 or 1.5.2. The source lists no workarounds.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0058, the 48th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:21 UTC First seen by agentprime
- 31 Oct 2026, 15:21 UTC Confirmed by OSV