{"answers":{"affected":"4 open source packages ship an affected version, including CoreWCF.UnixDomainSocket.","exploited":"There is no known exploitation of CVE-2026-54778 in the wild and no public exploit code.","fix":"Upgrade CoreWCF.UnixDomainSocket to a fixed version for your release line: 1.8.1 or 1.9.1.","what":"CVE-2026-54778 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-54778 and fix it if it is affected.\n\nWhat it is: CVE-2026-54778 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-54778 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- CoreWCF.UnixDomainSocket (NuGet): affected all versions; fixed in 1.8.1\n- CoreWCF.UnixDomainSocket (NuGet): affected all versions; fixed in 1.8.1\n- CoreWCF.UnixDomainSocket (NuGet): affected from 1.9.0; fixed in 1.9.1\n- CoreWCF.UnixDomainSocket (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-54778/ (Markdown: https://insights.sbomify.com/CVE-2026-54778/index.md)","id":"CVE-2026-54778","markdown":"https://insights.sbomify.com/CVE-2026-54778/index.md","name":"CVE-2026-54778","record":{"aliases":["GHSA-q6v9-43v5-jv9q"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CoreWCF library","requires_auth":"none","summary":"Concurrent connections in CoreWCF UnixDomainSocket identity resolution can cause identity misattribution or host crashes due to non-reentrant system calls.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-825","name":"Expired Pointer Dereference"},{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"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 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.","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: UnixDomainSocket Non-Reentrant POSIX Identity Resolution","id":"CVE-2026-54778","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":4,"n_references":6,"next":{"headline":"CoreWCF: SAML token replay protection is inoperative","id":"CVE-2026-54779"},"packages":[{"ecosystem":"NuGet","fixed":["1.8.1"],"introduced":["0"],"last_affected":[],"package":"CoreWCF.UnixDomainSocket","purl":null,"source":"GHSA-q6v9-43v5-jv9q"},{"ecosystem":"NuGet","fixed":["1.8.1"],"introduced":["0"],"last_affected":[],"package":"CoreWCF.UnixDomainSocket","purl":"pkg:nuget/CoreWCF.UnixDomainSocket","source":"GHSA-q6v9-43v5-jv9q"},{"ecosystem":"NuGet","fixed":["1.9.1"],"introduced":["1.9.0"],"last_affected":[],"package":"CoreWCF.UnixDomainSocket","purl":null,"source":"GHSA-q6v9-43v5-jv9q"},{"ecosystem":"NuGet","fixed":["1.9.1"],"introduced":["1.9.0"],"last_affected":[],"package":"CoreWCF.UnixDomainSocket","purl":"pkg:nuget/CoreWCF.UnixDomainSocket","source":"GHSA-q6v9-43v5-jv9q"}],"prev":{"headline":"CoreWCF NetNamedPipe transport accepts attach to a pre-existing named pipe instance","id":"CVE-2026-54777"},"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":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["CoreWCF"]},"summary":"Concurrent connections in CoreWCF UnixDomainSocket identity resolution can cause identity misattribution or host crashes due to non-reentrant system calls.","url":"https://insights.sbomify.com/CVE-2026-54778/"}