CVE-2026-10937

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-06-05. NVD baseline CVSS 6.5; sources differ by 0.0.

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

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

Inappropriate implementation in Passwords in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: High)

CVSS v3
6.5
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jun 12, 2026
No patch confirmed yet.
generic

Chromium

https://issues.chromium.org/issues/502651056
generic

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html

Vendor Advisories for CVE-2026-10937(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 148.0.7778.96-3 (363 versions)149.0.7827.53-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 149.0.7827.53-1~deb12u1 (129 versions)149.0.7827.53-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (130 versions)149.0.7827.53-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 87× 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 215 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-10937?
CVE-2026-10937 is a medium vulnerability published on June 4, 2026. Inappropriate implementation in Passwords in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-10937 disclosed?
CVE-2026-10937 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10937 actively exploited?
CVE-2026-10937 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 80.8% of all scored CVEs.
What is the CVSS score of CVE-2026-10937?
CVE-2026-10937 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-10937?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10937, 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-10937

Explore →

Is Your Infrastructure Affected by CVE-2026-10937?

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

Start Free Scan →Browse All CVEs