{"answers":{"affected":"4 open source packages ship an affected version, including CoreWCF.NetNamedPipe.","exploited":"There is no known exploitation of CVE-2026-54777 in the wild and no public exploit code.","fix":"Upgrade CoreWCF.NetNamedPipe to a fixed version for your release line: 1.8.1 or 1.9.1.","what":"CVE-2026-54777 is a medium-severity vulnerability in CoreWCF, published on 8 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54777 and fix it if it is affected.\n\nWhat it is: CVE-2026-54777 is a medium-severity vulnerability in CoreWCF, published on 8 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54777 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- CoreWCF.NetNamedPipe (NuGet): affected all versions; fixed in 1.8.1\n- CoreWCF.NetNamedPipe (NuGet): affected all versions; fixed in 1.8.1\n- CoreWCF.NetNamedPipe (NuGet): affected from 1.9.0; fixed in 1.9.1\n- CoreWCF.NetNamedPipe (NuGet): affected from 1.9.0; fixed in 1.9.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54777/ (Markdown: https://insights.sbomify.com/CVE-2026-54777/index.md)","id":"CVE-2026-54777","markdown":"https://insights.sbomify.com/CVE-2026-54777/index.md","name":"CVE-2026-54777","record":{"aliases":["GHSA-6jj2-4q5c-x8g6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CoreWCF library","requires_auth":"low_privilege","summary":"Local attackers can intercept NetNamedPipe traffic by racing service startup, exposing sensitive data in CoreWCF applications.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-665","name":"Improper Initialization"},{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"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 NetNamedPipe transport accepts attachment to a pre-existing named pipe instance, allowing local interception of NetNamedPipe traffic when an attacker races NamedPipeListener startup between shared memory GUID publication and service named pipe creation. This issue is fixed in versions 1.8.1 and 1.9.1.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"CoreWCF NetNamedPipe transport accepts attach to a pre-existing named pipe instance","id":"CVE-2026-54777","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"CoreWCF: UnixDomainSocket Non-Reentrant POSIX Identity Resolution","id":"CVE-2026-54778"},"packages":[{"ecosystem":"NuGet","fixed":["1.8.1"],"introduced":["0"],"last_affected":[],"package":"CoreWCF.NetNamedPipe","purl":null,"source":"GHSA-6jj2-4q5c-x8g6"},{"ecosystem":"NuGet","fixed":["1.8.1"],"introduced":["0"],"last_affected":[],"package":"CoreWCF.NetNamedPipe","purl":"pkg:nuget/CoreWCF.NetNamedPipe","source":"GHSA-6jj2-4q5c-x8g6"},{"ecosystem":"NuGet","fixed":["1.9.1"],"introduced":["1.9.0"],"last_affected":[],"package":"CoreWCF.NetNamedPipe","purl":null,"source":"GHSA-6jj2-4q5c-x8g6"},{"ecosystem":"NuGet","fixed":["1.9.1"],"introduced":["1.9.0"],"last_affected":[],"package":"CoreWCF.NetNamedPipe","purl":"pkg:nuget/CoreWCF.NetNamedPipe","source":"GHSA-6jj2-4q5c-x8g6"}],"prev":{"headline":"CoreWCF: Unix Domain Socket PosixIdentity transport accepts connections that skip the security upgrade","id":"CVE-2026-54776"},"products":["CoreWCF"],"published":"2026-07-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-10","vendors":["CoreWCF"]},"summary":"Local attackers can intercept NetNamedPipe traffic by racing service startup, exposing sensitive data in CoreWCF applications.","url":"https://insights.sbomify.com/CVE-2026-54777/"}