CoreWCF.NetNamedPipe
Affected
- introduced
0, fixed1.8.1(ecosystem)
Fixed versions
1.8.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-54777
CoreWCF NetNamedPipe transport accepts attach to a pre-existing named pipe instance
Impact
CoreWCF NetNamedPipe transport accepts attach to a pre-existing named pipe instance, allowing local interception of NetNamedPipe traffic. NetNamedPipe creates a shared memory object based on the listening url, then generated a unique GUID for the named pipe it will be using and saves this to the shared memory object. Then it creates the named pipe to listen for clients. This requires an attacker to race the service and create the named pipe between the service publishing the GUID to the shared memory location (which the attacker needs to read) and the service creating the named pipe itself.
Patches
Fixed in CoreWCF v1.8.1 and v1.9.1
Workarounds
None
Medium Basis: The source's own band: MODERATE
0, fixed 1.8.1 (ecosystem)1.8.1
The export has no generic command for this ecosystem.
1.9.0, fixed 1.9.1 (ecosystem)1.9.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0