CVE-2026-47634

HIGHNVD 5.47.3
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. NVD baseline CVSS 5.4; sources differ by 1.9.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
7.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.4Exploit: None knownExposed: 0

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

Improper neutralization of special elements in output used by a downstream component ('injection') in Microsoft Office SharePoint allows an authorized attacker to perform spoofing over a network.

CVSS v3
5.4
EG Score
7.3(medium)
EG Risk
33(Track)
EG Risk 33/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
Severity73% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 14, 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-47634

Vendor Advisories for CVE-2026-47634(2)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 97× 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 190 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-47634?
CVE-2026-47634 is a high vulnerability published on June 9, 2026. Improper neutralization of special elements in output used by a downstream component ('injection') in Microsoft Office SharePoint allows an authorized attacker to perform spoofing over a network.
When was CVE-2026-47634 disclosed?
CVE-2026-47634 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47634 actively exploited?
CVE-2026-47634 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.7% of all scored CVEs.
What is the CVSS score of CVE-2026-47634?
CVE-2026-47634 has a CVSS v3 base score of 5.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.3.
How do I remediate CVE-2026-47634?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47634, 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

Explore the affected products and dependency analysis for CVE-2026-47634

Explore →

Is Your Infrastructure Affected by CVE-2026-47634?

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