{"answers":{"affected":"4 open source packages ship an affected version, including CoreWCF.Primitives.","exploited":"There is no known exploitation of CVE-2026-54782 in the wild and no public exploit code.","fix":"Upgrade CoreWCF.Primitives to a fixed version for your release line: 1.8.1 or 1.9.1.","what":"CVE-2026-54782 is a critical authentication bypass 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-54782 and fix it if it is affected.\n\nWhat it is: CVE-2026-54782 is a critical authentication bypass 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-54782 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- CoreWCF.Primitives (NuGet): affected all versions; fixed in 1.8.1\n- CoreWCF.Primitives (NuGet): affected all versions; fixed in 1.8.1\n- CoreWCF.Primitives (NuGet): affected from 1.9.0; fixed in 1.9.1\n- CoreWCF.Primitives (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-54782/ (Markdown: https://insights.sbomify.com/CVE-2026-54782/index.md)","id":"CVE-2026-54782","markdown":"https://insights.sbomify.com/CVE-2026-54782/index.md","name":"CVE-2026-54782","record":{"aliases":["GHSA-xjr9-gg9q-jx3v"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"CoreWCF library","requires_auth":"none","summary":"An unauthenticated attacker can impersonate any principal in CoreWCF applications using federated bindings due to flawed SAML token signature validation.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"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 SAML 1.1 and SAML 2.0 token validation does not correctly resolve the issuer signing key or require signed tokens when IdentityConfiguration is used with federated bindings, allowing an unauthenticated remote attacker to impersonate any principal the trusted STS could issue. 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: Authentication bypass in CoreWCF SAML 1.1 / 2.0 token signature validation","id":"CVE-2026-54782","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":4,"n_references":6,"next":{"headline":"CoreWCF: XML Signature Wrapping in WS-Security endorsing/supporting signature verification allows replay of captured signed messages","id":"CVE-2026-54783"},"packages":[{"ecosystem":"NuGet","fixed":["1.8.1"],"introduced":["0"],"last_affected":[],"package":"CoreWCF.Primitives","purl":null,"source":"GHSA-xjr9-gg9q-jx3v"},{"ecosystem":"NuGet","fixed":["1.8.1"],"introduced":["0"],"last_affected":[],"package":"CoreWCF.Primitives","purl":"pkg:nuget/CoreWCF.Primitives","source":"GHSA-xjr9-gg9q-jx3v"},{"ecosystem":"NuGet","fixed":["1.9.1"],"introduced":["1.9.0"],"last_affected":[],"package":"CoreWCF.Primitives","purl":null,"source":"GHSA-xjr9-gg9q-jx3v"},{"ecosystem":"NuGet","fixed":["1.9.1"],"introduced":["1.9.0"],"last_affected":[],"package":"CoreWCF.Primitives","purl":"pkg:nuget/CoreWCF.Primitives","source":"GHSA-xjr9-gg9q-jx3v"}],"prev":{"headline":"CoreWCF: SAML SubjectConfirmation methods and holder-of-key proof keys are not enforced","id":"CVE-2026-54781"},"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":"total"},"state":"PUBLISHED","updated":"2026-07-10","vendors":["CoreWCF"]},"summary":"An unauthenticated attacker can impersonate any principal in CoreWCF applications using federated bindings due to flawed SAML token signature validation.","url":"https://insights.sbomify.com/CVE-2026-54782/"}