{"answers":{"affected":"4 open source packages ship an affected version, including CoreWCF.Primitives.","exploited":"There is no known exploitation of CVE-2026-54774 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-54774 is a high-severity 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-54774 and fix it if it is affected.\n\nWhat it is: CVE-2026-54774 is a high-severity 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-54774 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-54774/ (Markdown: https://insights.sbomify.com/CVE-2026-54774/index.md)","id":"CVE-2026-54774","markdown":"https://insights.sbomify.com/CVE-2026-54774/index.md","name":"CVE-2026-54774","record":{"aliases":["GHSA-rpj7-hr7h-w6p9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"CoreWCF library","requires_auth":"none","summary":"Attackers can bypass SAML assertion signature verification in CoreWCF services by using non-X.509 signing tokens, undermining authentication integrity.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"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, SamlSerializer skips final SignatureValue verification when a CoreWCF service validates SAML tokens using a non-X.509 signing token, allowing an attacker to reference a non-X.509 SecurityToken key identifier and bypass assertion signature verification. 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: SamlSerializer skips SignatureValue verification when SAML signing token is not an X.509 certificate","id":"CVE-2026-54774","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":4,"n_references":6,"next":{"headline":"CoreWCF: Kafka consume pump halts permanently on a Kafka tombstone (null-value record), causing persistent endpoint denial of service.","id":"CVE-2026-54775"},"packages":[{"ecosystem":"NuGet","fixed":["1.8.1"],"introduced":["0"],"last_affected":[],"package":"CoreWCF.Primitives","purl":null,"source":"GHSA-rpj7-hr7h-w6p9"},{"ecosystem":"NuGet","fixed":["1.8.1"],"introduced":["0"],"last_affected":[],"package":"CoreWCF.Primitives","purl":"pkg:nuget/CoreWCF.Primitives","source":"GHSA-rpj7-hr7h-w6p9"},{"ecosystem":"NuGet","fixed":["1.9.1"],"introduced":["1.9.0"],"last_affected":[],"package":"CoreWCF.Primitives","purl":null,"source":"GHSA-rpj7-hr7h-w6p9"},{"ecosystem":"NuGet","fixed":["1.9.1"],"introduced":["1.9.0"],"last_affected":[],"package":"CoreWCF.Primitives","purl":"pkg:nuget/CoreWCF.Primitives","source":"GHSA-rpj7-hr7h-w6p9"}],"prev":{"headline":"CoreWCF: WS-Security signature substitution via document-wide Signature lookup","id":"CVE-2026-54773"},"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":"Attackers can bypass SAML assertion signature verification in CoreWCF services by using non-X.509 signing tokens, undermining authentication integrity.","url":"https://insights.sbomify.com/CVE-2026-54774/"}