CVE-2026-9960

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

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

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

Integer overflow in PDFium in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to execute arbitrary code inside a sandbox via a crafted font file. (Chromium security severity: High)

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

Published

May 28, 2026

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Jun 4, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-9960(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 / 84× 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 292 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-9960?
CVE-2026-9960 is a high vulnerability published on May 28, 2026. Integer overflow in PDFium in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to execute arbitrary code inside a sandbox via a crafted font file. (Chromium security severity: High)
When was CVE-2026-9960 disclosed?
CVE-2026-9960 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-9960 actively exploited?
CVE-2026-9960 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 85.7% of all scored CVEs.
What is the CVSS score of CVE-2026-9960?
CVE-2026-9960 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-9960?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9960, 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-9960

Explore →

Is Your Infrastructure Affected by CVE-2026-9960?

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