# CVE-2026-54778 — CoreWCF

> As of 2026-07-09, CVE-2026-54778 is a MEDIUM-severity vulnerability in CoreWCF, CVSS v3.1 6.2, EPSS 0.1% (1.0th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-54778 as of 2026-07-09; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-07-09

## What is CVE-2026-54778?

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 UnixDomainSocket POSIX peer identity resolution uses non-reentrant getpwuid and getgrgid calls, allowing concurrent connections to attribute one connection's identity to another or crash the host process under contention. This issue is fixed in versions 1.8.1 and 1.9.1.

The record classifies CVE-2026-54778 under weakness classes [CWE-362](https://intel.threadlinqs.com/cwe/CWE-362), [CWE-825](https://cwe.mitre.org/data/definitions/825.html). Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 89 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 6.2 — MEDIUM (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **EPSS (FIRST):** 0.1% probability of exploitation in the next 30 days, higher than 1.0% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-08, last modified 2026-07-09

## Is CVE-2026-54778 being exploited?

It currently carries a trending score of 29 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [CoreWCF](https://intel.threadlinqs.com/vendors/corewcf): CoreWCF

Affected software packages:

- `nuget:CoreWCF.UnixDomainSocket` — patched in 1.8.1
- `nuget:CoreWCF.UnixDomainSocket` — patched in 1.9.1

## How to fix CVE-2026-54778

Fixed versions are recorded for 2 packages: nuget:CoreWCF.UnixDomainSocket 1.8.1, nuget:CoreWCF.UnixDomainSocket 1.9.1. No vendor patch reference has been recorded for CVE-2026-54778 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-54778

No threat campaign in the Threadlinqs corpus currently references CVE-2026-54778, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on 2026-07-12. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/CoreWCF/CoreWCF/security/advisories/GHSA-q6v9-43v5-jv9q)

**Other references**

- [github.com](https://github.com/CoreWCF/CoreWCF/commit/a3d95ea4627b818995e92c7def4c016164cacfce)
- [github.com (b0acb105589b455a095ea5ff49f5191e4eeff791)](https://github.com/CoreWCF/CoreWCF/commit/b0acb105589b455a095ea5ff49f5191e4eeff791)
- [github.com (b4867547c94bb088568935d581a55dda18a621e1)](https://github.com/CoreWCF/CoreWCF/commit/b4867547c94bb088568935d581a55dda18a621e1)
- [github.com (v1.8)](https://github.com/CoreWCF/CoreWCF/releases/tag/v1.8.1)
- [github.com (v1.9)](https://github.com/CoreWCF/CoreWCF/releases/tag/v1.9.1)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-54778
Full detection coverage and IOCs for threats exploiting CVE-2026-54778 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp