Memory corruption via crafted PDF heap overflow
Published Feb 18, 2026 · Updated Feb 18, 2026
Heap buffer overflow in PDFium in Google Chrome before 145.0.7632.109 allows remote attackers to write outside heap bounds via a crafted PDF file. Google has not disclosed the affected PDFium routine or the incorrect allocation, bounds check, or write operation that causes the overflow. Opening or rendering the attacker-supplied PDF is required, after which the out-of-bounds write corrupts Chrome process memory.
Summary
What happened
Heap buffer overflow in PDFium in Google Chrome before 145.0.7632.109 allows remote attackers to write outside heap bounds via a crafted PDF file. Google has not disclosed the affected PDFium routine or the incorrect allocation, bounds check, or write operation that causes the overflow. Opening or rendering the attacker-supplied PDF is required, after which the out-of-bounds write corrupts Chrome process memory.
The record
- CVE
- CVE-2026-2648
- Published
- Feb 18, 2026
- Updated
- Feb 18, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-122, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2026CVE publishedPublication date reported by the CVE source.
- Feb 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=145.0.7632.109 <145.0.7632.109
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo