CVE-2026-6361

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)

Published: 2026-04-15 Last update: 2026-05-26 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-6361 is rated Low Risk (34.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-6361

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-16 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-6361

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.3 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.6 6.0 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-6361

GitHub Security Advisory for CVE-2026-6361

GHSA-q3hg-2w34-64m3 · Severity: high — Heap buffer overflow in PDFium in Google Chrome on Windows prior to 147.0.7727.101 allowed a...

OS Trackers for CVE-2026-6361

vendor priority summary link
debian end-of-life CVE-2026-6361 end-of-life priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2026-6361
redhat high — https://access.redhat.com/security/cve/CVE-2026-6361
ubuntu medium CVE-2026-6361 medium priority: Ubuntu including 1 source packages (chromium-browser), 4 status rows across 4 suites (jammy, noble, questing, upstream): not-affected 3, released 1. https://ubuntu.com/security/CVE-2026-6361

Affected software / configurations for CVE-2026-6361

Vendor Product Version Raw CPE
google chrome < 147.0.7727.101 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

References for CVE-2026-6361

cvelogic Threat Intelligence