CVE-2026-54773

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: CVSS: 5.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

CoreWCF: WS-Security signature substitution via document-wide Signature lookup

Impact

An unauthenticated remote attacker who can place a SOAP header lexically before wsse:Security can embed a ds:Signature of their choosing inside that header and cause the server to verify the attacker-supplied signature instead of the one carried in the security header.

Preconditions

Exploitation requires the endpoint be configured with an endorsing supporting token binding, and the attacker constructs a ds:Signature whose KeyInfo resolves through the receive-side token resolver to a key under the attacker’s control. Both are conditions outside the attacker’s direct control on a generic deployment.

Patches

Fixed in CoreWCF v1.8.1 and v1.9.1

Workarounds

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).

CVSS v3
5.9
EG Score
5.9(low)
EPSS
KEV
Not listed

Published

June 19, 2026

Last Modified

June 19, 2026

Vendor Advisories for CVE-2026-54773(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
CoreWCF.Primitives1.9.01.9.1

Data Freshness Timeline

(refreshed 7× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:11 UTCEG score recompute
  2. 2026-07-05 17:52 UTCEG score recompute
  3. 2026-07-04 19:35 UTCEG score recompute
  4. 2026-07-03 21:14 UTCEG score recompute
  5. 2026-07-02 23:00 UTCEG score recompute
  6. 2026-07-02 00:46 UTCEG score recompute
  7. 2026-07-01 02:28 UTCEG score recompute
  8. 2026-06-30 04:14 UTCEG score recompute
  9. 2026-06-29 05:58 UTCEG score recompute
  10. 2026-06-28 07:42 UTCEG score recompute
  11. 2026-06-27 09:28 UTCEG score recompute
  12. 2026-06-26 11:14 UTCEG score recompute
  13. 2026-06-25 11:01 UTCEG score recompute
  14. 2026-06-24 12:48 UTCEG score recompute
  15. 2026-06-23 14:33 UTCEG score recompute
  16. 2026-06-22 16:15 UTCEG score recompute
  17. 2026-06-21 18:00 UTCEG score recompute
  18. 2026-06-20 19:42 UTCEG score recompute
  19. 2026-06-19 21:25 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-54773?
CVE-2026-54773 is a medium vulnerability published on June 19, 2026. CoreWCF: WS-Security signature substitution via document-wide Signature lookup Impact An unauthenticated remote attacker who can place a SOAP header lexically before wsse:Security can embed a ds:Signature of their choosing inside that header and cause the server to verify the attacker-supplied…
When was CVE-2026-54773 disclosed?
CVE-2026-54773 was first published in the National Vulnerability Database on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-54773?
CVE-2026-54773 has a CVSS v4.0 base score of 5.9 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-54773?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54773, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54773

Explore →

Is Your Infrastructure Affected by CVE-2026-54773?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.