LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2648: Heap buffer overflow in PDFium in Google Chrome prior to 145.0.7632.109 allowed a remote attacker to perfor...

Heap buffer overflow in PDFium in Google Chrome prior to 145.0.7632.109 allowed a remote attacker to perform an out of bounds memory write via a crafted PDF file. (Chromium security severity: High)

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-2648 is a high-severity Chrome flaw in PDFium, Chrome’s PDF handling component. A malicious PDF could cause memory corruption and potentially let an attacker run code or compromise browser data after a user opens it. Google fixed it in Chrome 145.0.7632.109. No provided source says it is being actively exploited.

Executive priority

Treat this as a prompt browser update priority. The vulnerability has high technical impact and can be reached through a common user action, opening a PDF. It is not supported as actively exploited by the provided sources, so urgency is high but not emergency-level based on current evidence.

Technical view

The issue is a heap buffer overflow, CWE-122, in PDFium before Google Chrome 145.0.7632.109. The CVSS 3.1 score is 8.8, with network attack vector, low complexity, no privileges required, and user interaction required. The impact ratings are high for confidentiality, integrity, and availability. Triggering requires a crafted PDF file.

Likely exposure

Organizations are exposed where desktop Google Chrome installations are older than 145.0.7632.109 and users can open PDFs from email, websites, or downloads. Exposure is higher in environments without rapid browser auto-update enforcement or where Chrome’s built-in PDF viewer is commonly used.

Exploitation context

The documented attack path is a crafted PDF file processed by Chrome/PDFium. User interaction is required. The source bundle does not include public exploit details, weaponization evidence, or CISA KEV listing, so active exploitation should not be assumed.

Researcher notes

The Chromium issue link may have restricted details. Available public data identifies PDFium heap overflow and crafted PDF trigger, but not root cause, exploitability constraints, or indicators of compromise. Avoid assuming affected Chromium-based products beyond Google Chrome unless separately confirmed by their vendors.

Mitigation direction

  • Update Google Chrome desktop to 145.0.7632.109 or later.
  • Confirm browser auto-update is enabled and functioning across managed endpoints.
  • Prioritize users who routinely handle external PDFs.
  • Review Google Chrome release guidance for any additional vendor instructions.

Validation and detection

  • Inventory Chrome versions across endpoints and flag versions below 145.0.7632.109.
  • Verify updated endpoints report Chrome 145.0.7632.109 or later.
  • Check browser management telemetry for failed or deferred updates.
  • Confirm PDF handling policies align with organizational risk tolerance.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2648 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-2648Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChrome145.0.7632.109Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.