CVE-2026-10002

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-29. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

Use after free in PDFium in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. (Chromium security severity: High)

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

Published

May 28, 2026

Last Modified

July 21, 2026

Advisory Details (2)

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

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html

Vendor Advisories for CVE-2026-10002(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 (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—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-3 (126 versions)148.0.7778.215-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 91× 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 326 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-10002?
CVE-2026-10002 is a high vulnerability published on May 28, 2026. Use after free in PDFium in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. (Chromium security severity: High)
When was CVE-2026-10002 disclosed?
CVE-2026-10002 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-10002 actively exploited?
CVE-2026-10002 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 92.4% of all scored CVEs.
What is the CVSS score of CVE-2026-10002?
CVE-2026-10002 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-10002?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10002, 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-10002

Explore →

Is Your Infrastructure Affected by CVE-2026-10002?

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

Start Free Scan →Browse All CVEs