CVE-2026-34327

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-05-08. The CNA's CVSS baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
8.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Externally controlled reference to a resource in another sphere in Microsoft Partner Center allows an unauthorized attacker to perform spoofing over a network.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity82% × 45%
The EG Score, 8.2 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

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

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

May 7, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated May 7, 2026
Fix referenced — no release confirmed yet. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

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

Vendor Advisories for CVE-2026-34327(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 27× 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 98 of 290 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 192 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-34327?
CVE-2026-34327 is a high-severity vulnerability; its CVE record was published on May 7, 2026. Externally controlled reference to a resource in another sphere in Microsoft Partner Center allows an unauthorized attacker to perform spoofing over a network.
When was CVE-2026-34327 made public?
CVE-2026-34327 was made public on May 7, 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 May 7, 2026. EchelonGraph's copy of the record carries a last-modified date of August 10, 2026; the record at its source may have been updated since.
Is CVE-2026-34327 actively exploited?
CVE-2026-34327 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-34327?
CVE-2026-34327 has a CVSS base score of 8.2 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-34327?
A fix for CVE-2026-34327 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-34327 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-34327?

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

Book a Demo →Browse All CVEs