{"answers":{"affected":"4 open source packages ship an affected version, including CoreWCF.NetFramingBase.","exploited":"There is no known exploitation of CVE-2026-54772 in the wild and no public exploit code.","fix":"Upgrade CoreWCF.NetFramingBase to a fixed version for your release line: 1.8.1 or 1.9.1.","what":"CVE-2026-54772 is a high-severity denial of service vulnerability in CoreWCF, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54772 and fix it if it is affected.\n\nWhat it is: CVE-2026-54772 is a high-severity denial of service vulnerability in CoreWCF, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54772 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- CoreWCF.NetFramingBase (NuGet): affected all versions; fixed in 1.8.1\n- CoreWCF.NetFramingBase (NuGet): affected all versions; fixed in 1.8.1\n- CoreWCF.NetFramingBase (NuGet): affected from 1.9.0; fixed in 1.9.1\n- CoreWCF.NetFramingBase (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-54772/ (Markdown: https://insights.sbomify.com/CVE-2026-54772/index.md)","id":"CVE-2026-54772","markdown":"https://insights.sbomify.com/CVE-2026-54772/index.md","name":"CVE-2026-54772","record":{"aliases":["GHSA-p86g-xrr2-pf7c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"CoreWCF library","requires_auth":"none","summary":"Unauthenticated attackers can cause CPU exhaustion and denial of service in CoreWCF applications by triggering infinite loops during network framing handshakes.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-835","name":"Loop with Unreachable Exit Condition"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"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, an unauthenticated remote attacker that can reach a NetTcpBinding, NetNamedPipeBinding, or UnixDomainSocketBinding endpoint can trigger premature EOF handling in the CoreWCF net.tcp, net.pipe, or net.uds framing handshake and pin one server thread-pool worker at full CPU per connection. 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: Pre-authentication infinite-loop CPU exhaustion in CoreWCF net.tcp / net.pipe / net.uds framing handshake","id":"CVE-2026-54772","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":4,"n_references":6,"next":{"headline":"CoreWCF: WS-Security signature substitution via document-wide Signature lookup","id":"CVE-2026-54773"},"packages":[{"ecosystem":"NuGet","fixed":["1.8.1"],"introduced":["0"],"last_affected":[],"package":"CoreWCF.NetFramingBase","purl":null,"source":"GHSA-p86g-xrr2-pf7c"},{"ecosystem":"NuGet","fixed":["1.8.1"],"introduced":["0"],"last_affected":[],"package":"CoreWCF.NetFramingBase","purl":"pkg:nuget/CoreWCF.NetFramingBase","source":"GHSA-p86g-xrr2-pf7c"},{"ecosystem":"NuGet","fixed":["1.9.1"],"introduced":["1.9.0"],"last_affected":[],"package":"CoreWCF.NetFramingBase","purl":null,"source":"GHSA-p86g-xrr2-pf7c"},{"ecosystem":"NuGet","fixed":["1.9.1"],"introduced":["1.9.0"],"last_affected":[],"package":"CoreWCF.NetFramingBase","purl":"pkg:nuget/CoreWCF.NetFramingBase","source":"GHSA-p86g-xrr2-pf7c"}],"prev":{"headline":"Langroid: handle_message() executes user-supplied tool JSON without sender verification","id":"CVE-2026-54771"},"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["CoreWCF"]},"summary":"Unauthenticated attackers can cause CPU exhaustion and denial of service in CoreWCF applications by triggering infinite loops during network framing handshakes.","url":"https://insights.sbomify.com/CVE-2026-54772/"}