CVE-2026-4455: Heap buffer overflow in PDFium
Chromium: CVE-2026-4455 Heap buffer overflow in PDFium
Other sources
Heap buffer overflow in PDFium in Google Chrome prior to 146.0.7680.153 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. (Chromium security severity: High)
— NVD
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
Credit
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-4439
- CVE-2026-4440
- CVE-2026-4441
- CVE-2026-4442
- CVE-2026-4443
- CVE-2026-4444
- CVE-2026-4445
- CVE-2026-4446
- CVE-2026-4447
- CVE-2026-4448
- CVE-2026-4449
- CVE-2026-4450
- CVE-2026-4451
- CVE-2026-4452
- CVE-2026-4453
- CVE-2026-4454
- CVE-2026-4456
- CVE-2026-4457
- CVE-2026-4458
- CVE-2026-4459
- CVE-2026-4460
- CVE-2026-4461
- CVE-2026-4462
- CVE-2026-4463
- CVE-2026-4464
Frequently Asked Questions
What is the severity of CVE-2026-4455?
The severity of CVE-2026-4455 is classified as High due to the potential for remote exploitation.
What causes CVE-2026-4455?
CVE-2026-4455 is caused by a heap buffer overflow in PDFium that can be triggered by a crafted PDF file.
Which versions of Google Chrome are affected by CVE-2026-4455?
Google Chrome versions prior to 146.0.7680.153 are affected by CVE-2026-4455.
How do I fix CVE-2026-4455?
To fix CVE-2026-4455, update Google Chrome to version 146.0.7680.153 or later.
Can CVE-2026-4455 affect other browsers?
CVE-2026-4455 primarily affects Google Chrome but may also impact Chromium-based browsers if they use the vulnerable PDFium.