CVE-2026-6361

HIGHNVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
8.3EG
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.3Exploit: None knownExposed: 0

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

Heap buffer overflow in PDFium in Google Chrome on Windows prior to 147.0.7727.101 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code inside a sandbox via a crafted PDF file. (Chromium security severity: High)

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

Published

April 15, 2026

Last Modified

May 26, 2026

Advisory Details (2)

Auto-updated Apr 29, 2026
No patch confirmed yet.
generic

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop_15.html

Vendor Advisories for CVE-2026-6361(1)

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 ... 147.0.7727.55-1~deb13u1 (339 versions)147.0.7727.101-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 147.0.7727.55-1~deb13u1 (105 versions)147.0.7727.101-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 147.0.7727.55-1~deb13u1 (106 versions)147.0.7727.101-1—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-6361?
CVE-2026-6361 is a high vulnerability published on April 15, 2026. Heap buffer overflow in PDFium in Google Chrome on Windows prior to 147.0.7727.101 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code inside a sandbox via a crafted PDF file. (Chromium security severity: High)
When was CVE-2026-6361 disclosed?
CVE-2026-6361 was first published in the National Vulnerability Database on April 15, 2026, with the most recent update on May 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6361 actively exploited?
CVE-2026-6361 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 76.3% of all scored CVEs.
What is the CVSS score of CVE-2026-6361?
CVE-2026-6361 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-6361?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6361, 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-6361

Explore →

Is Your Infrastructure Affected by CVE-2026-6361?

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

Start Free Scan →Browse All CVEs