CVE-2026-10011

LOWPre-NVD 3.13.1—
EchelonGraph scoreMEDIUM confidence

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-05-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 3.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.1Exploit: None knownExposed: 0

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

Inappropriate implementation in Skia in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

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

Published

May 28, 2026

Last Modified

July 21, 2026

References (2)

Vendor Advisories for CVE-2026-10011(2)

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

Affected Packages

(5 across 4 ecosystems)
Debian:14(2)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-3 (126 versions)148.0.7778.215-1—
libskia146.20260311+dfsg-1 ... 146.20260414~git.ef5f213+dfsg-4 (8 versions)146.20260414~git.ef5f213+dfsg-5—
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 (359 versions)148.0.7778.215-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-3 (125 versions)148.0.7778.215-1~deb13u1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 40× 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 168 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-10011?
CVE-2026-10011 is a low vulnerability published on May 28, 2026. Inappropriate implementation in Skia in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-10011 disclosed?
CVE-2026-10011 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10011 actively exploited?
CVE-2026-10011 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 94.2% of all scored CVEs.
What is the CVSS score of CVE-2026-10011?
CVE-2026-10011 has a CVSS v3.1 base score of 3.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-10011?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10011, 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-10011

Explore →

Is Your Infrastructure Affected by CVE-2026-10011?

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

Start Free Scan →Browse All CVEs