CVE-2026-62828

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

Score 5.4 from GitHub Security Advisory (severity: MODERATE) published 2026-07-28. A secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-49870 (ENISA EUVD) · GHSA-7p27-g9vh-5fqj (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper input validation in Microsoft Edge for Android allows an unauthorized attacker to perform tampering over a network.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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 available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

July 28, 2026

Last Modified

November 10, 2026

Advisory Details (1)

Auto-updated Jul 28, 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-62828

Vendor Advisories for CVE-2026-62828(2)

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 9× in last 7d / 37× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 316 rows on record for this CVE, as 98 entries (2 repeats merged).

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 216 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62828?
CVE-2026-62828 is a medium-severity vulnerability; its CVE record was published on July 28, 2026. Improper input validation in Microsoft Edge for Android allows an unauthorized attacker to perform tampering over a network.
When was CVE-2026-62828 made public?
CVE-2026-62828 was made public on July 16, 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 28, 2026. EchelonGraph's copy of the record carries a last-modified date of November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-62828 actively exploited?
CVE-2026-62828 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62828?
CVE-2026-62828 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62828?
A fix for CVE-2026-62828 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62828 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-62828?

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

Book a Demo →Browse All CVEs