CVE-2026-47304

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. 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: epss, nvd
Trending — Patch released this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

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.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

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
Severity98% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

July 14, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 28, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

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

Vendor Advisories for CVE-2026-47304(18)

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

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntudotnet10 (10.0.110-10.0.10-0ubuntu1~26.04.1) @ resolute2026-08-30ubuntu
redhatdotnet9.0-0:9.0.120-1.el9_62026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_62026-08-24redhat
redhatdotnet9.0-0:9.0.120-1.el10_02026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_42026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el10_02026-08-24redhat
redhatdotnet9.0-0:9.0.119-1.el10_22026-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
redhatdotnet8-0-main-8.0.129-2.1.hum12026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el9_82026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el8_102026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el8_102026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el9_82026-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 rangeFixed inDependents
System.Security.Cryptography.Xml8.0.0, 8.0.1, 8.0.2, 8.0.38.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 39× in last 7d / 235× 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.

Showing the most recent 100 of 307 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47304?
CVE-2026-47304 is a critical vulnerability 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 disclosed?
CVE-2026-47304 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47304 actively exploited?
CVE-2026-47304 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.2% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47304, 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-47304

Explore →

Is Your Infrastructure Affected by CVE-2026-47304?

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

Start Free Scan →Browse All CVEs