← Back
CVE-2026-54773
medium
CVSS 5.9
Vulnerability in CoreWCF.Primitives (CVE-2026-54773)
Summary
vulnerability in CoreWCF.Primitives (CVE-2026-54773). Data can be tampered with by attackers. Exploitable via ``KeyInfo``. Mitigation: upgrade to `1.9.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54773** has been found in CoreWCF.Primitives.
Attackers can target a specific entry point like ``KeyInfo`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.9/10.
What to do: upgrade CoreWCF.Primitives to **1.9.1** or later.
If unsure, ask your IT team or search "CoreWCF.Primitives CVE-2026-54773" on the vendor's site.
CVE-2026-54773 (CoreWCF.Primitives) — CWE-347 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `KeyInfo`
Patched: `1.9.1` — apply immediately
Workaround: Use a security token resolver that only accepts references to issuer-pinned X.509 chains (the default when expecting a static set of signing certificates).
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-347) exists in CoreWCF.Primitives. Attackers reach the vulnerable code path via ``KeyInfo`` without authentication.
📍 Affected scope
CoreWCF.Primitives — . Attack surface: `KeyInfo`.
🔥 Severity
Severity: Medium (CVSS 5.9/10). Data can be tampered with by attackers
🔧 How to fix
Update to **1.9.1**.
🛡️ Workaround
Workaround: Use a security token resolver that only accepts references to issuer-pinned X.509 chains (the default when expecting a static set of signing certificates).
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'CoreWCF.Primitives' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'CoreWCF.Primitives' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `CoreWCF.Primitives` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Use a security token resolver that only accepts references to issuer-pinned X.509 chains (the default when expecting a static set of signing certificates).パッチが適用されるまでの応急処置として、Use a security token resolver that only accepts references to issuer-pinned X.509 chains (the default when expecting a static set of signing certificates). を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade CoreWCF.Primitives to 1.9.1ステージング環境で 1.9.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
nuget
CoreWCF.Primitives
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.9.1"}]}]