CVE-2026-47304

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3% (19th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper verification of cryptographic signature in .NET allows an unauthorized attacker to bypass a security feature over a network.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47304

Patch Availability(17)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntudotnet10 (10.0.110-10.0.10-0ubuntu1~26.04.1) @ resolute2026-10-13ubuntu
redhatdotnet8.0-0:8.0.130-1.el10_02026-08-24redhat
redhatdotnet9.0-0:9.0.120-1.el10_02026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_62026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_42026-08-24redhat
redhatdotnet9.0-0:9.0.120-1.el9_62026-08-24redhat
redhatdotnet8-0-main-8.0.29-2.1.hum12026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el10_22026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el8_102026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el9_82026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el8_102026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el9_82026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el8_102026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el9_82026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el10_22026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el10_22026-07-20redhat
redhatdotnet9-0-main-9.0.119-1.hum12026-07-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFix by version rangeDependents
System.Security.Cryptography.Xml8.0.0, 8.0.1, 8.0.2, 8.0.3
  • 10.0.0 up to 10.0.10: fixed in 10.0.10
  • 9.0.0 up to 9.0.18: fixed in 9.0.18
  • 8.0.0 up to 8.0.4: fixed in 8.0.4
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 18× in last 7d / 50× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 409 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 309 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 09:06 UTCEG score recompute
  2. 2026-10-14 09:06 UTCVendor advisory
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-13 05:59 UTCEG score recompute
  5. 2026-10-13 05:59 UTCVendor advisory
  6. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-10-12 16:02 UTCEG score recompute
  8. 2026-10-12 07:31 UTCVendor advisory
  9. 2026-10-11 19:44 UTCEG score recompute
  10. 2026-10-11 16:59 UTCEG score recompute
  11. 2026-10-11 14:24 UTCEG score recompute
  12. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-08 19:15 UTCEG score recompute
  16. 2026-10-08 19:15 UTCVendor advisory
  17. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  24. 2026-10-01 12:53 UTCEG score recompute
  25. 2026-10-01 12:53 UTCVendor advisory
Show 75 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-09-28 13:16 UTCVendor advisory
  4. 2026-09-28 08:56 UTCEG score recompute
  5. 2026-09-28 08:56 UTCVendor advisory
  6. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-09-25 18:40 UTCEG score recompute
  10. 2026-09-25 18:40 UTCVendor advisory
  11. 2026-09-24 09:01 UTCEG score recompute
  12. 2026-09-24 09:01 UTCVendor advisory
  13. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  14. 2026-09-23 10:59 UTCVendor advisory
  15. 2026-09-23 07:11 UTCVendor advisory
  16. 2026-09-23 03:32 UTCEG score recompute
  17. 2026-09-23 03:32 UTCVendor advisory
  18. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  19. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-09-18 10:01 UTCVendor advisory
  21. 2026-09-18 04:52 UTCVendor advisory
  22. 2026-09-17 22:49 UTCEG score recompute
  23. 2026-09-17 22:49 UTCVendor advisory
  24. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  26. 2026-09-14 10:24 UTCVendor advisory
  27. 2026-09-14 06:44 UTCVendor advisory
  28. 2026-09-14 03:05 UTCVendor advisory
  29. 2026-09-13 23:16 UTCEG score recompute
  30. 2026-09-13 23:16 UTCVendor advisory
  31. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  32. 2026-09-13 16:26 UTCVendor advisory
  33. 2026-09-13 11:50 UTCVendor advisory
  34. 2026-09-13 07:40 UTCVendor advisory
  35. 2026-09-12 16:52 UTCEG score recompute
  36. 2026-09-12 16:52 UTCVendor advisory
  37. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  38. 2026-09-12 13:13 UTCVendor advisory
  39. 2026-09-12 07:27 UTCVendor advisory
  40. 2026-09-12 01:37 UTCVendor advisory
  41. 2026-09-11 21:56 UTCEG score recompute
  42. 2026-09-11 21:56 UTCVendor advisory
  43. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  44. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  45. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  46. 2026-09-09 21:07 UTCVendor advisory
  47. 2026-09-08 22:42 UTCEG score recompute
  48. 2026-09-08 22:42 UTCVendor advisory
  49. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  50. 2026-09-08 21:06 UTCVendor advisory
  51. 2026-09-08 17:18 UTCVendor advisory
  52. 2026-09-08 01:12 UTCEG score recompute
  53. 2026-09-08 01:12 UTCVendor advisory
  54. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  55. 2026-09-06 17:48 UTCEG score recompute
  56. 2026-09-06 17:48 UTCVendor advisory
  57. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  58. 2026-09-06 13:32 UTCVendor advisory
  59. 2026-09-06 04:35 UTCVendor advisory
  60. 2026-09-06 00:44 UTCVendor advisory
  61. 2026-09-05 21:01 UTCEG score recompute
  62. 2026-09-05 21:01 UTCVendor advisory
  63. 2026-09-04 22:39 UTCEG score recompute
  64. 2026-09-04 22:39 UTCVendor advisory
  65. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  66. 2026-09-02 19:39 UTCEG score recompute
  67. 2026-09-02 19:39 UTCVendor advisory
  68. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  69. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  70. 2026-08-31 15:39 UTCVendor advisory
  71. 2026-08-31 04:41 UTCVendor advisory
  72. 2026-08-30 23:29 UTCVendor advisory
  73. 2026-08-30 19:50 UTCEG score recompute
  74. 2026-08-30 19:50 UTCVendor advisory
  75. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 11th percentile

Frequently asked(5)

What is CVE-2026-47304?
CVE-2026-47304 is a critical-severity vulnerability; its CVE record was published on July 14, 2026. Improper verification of cryptographic signature in .NET allows an unauthorized attacker to bypass a security feature over a network.
When was CVE-2026-47304 made public?
CVE-2026-47304 was made public on July 14, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-47304 actively exploited?
CVE-2026-47304 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47304?
CVE-2026-47304 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-47304?
A fix for CVE-2026-47304 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47304 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-47304?

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