Secuno
ENNL
Book demo

CVE-2026-87585

8.8 HIGHEPSS 0.28%
  1. Published8 Sept 2026

Description

Double free in PDFium in Google Chrome on on Windows prior to 153.0.8010.36 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted PDF file. (Chromium security severity: High)

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

Google Chrome< 153.0.8010.36

Remediation

Fixed in
Google Chrome≥ 153.0.8010.36

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-859218.2
Double free in Windows Secure Kernel Mode allows an authorized attacker to elevate…
CVE-2026-800808.8
Double free in Microsoft Office Word allows an unauthorized attacker to execute code…
CVE-2026-775048.8
Double free in Microsoft Office Word allows an unauthorized attacker to execute code…
CVE-2026-774939.8
Double free in Microsoft Graphics Component allows an unauthorized attacker to execute…
CVE-2026-729588.2
Double free in Windows Credential Guard allows an authorized attacker to elevate…
CVE-2026-698768.0
Use after free in Windows DHCP Server allows an authorized attacker to execute code…

Frequently asked

Is CVE-2026-87585 being actively exploited?

CVE-2026-87585 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.28%.

How severe is CVE-2026-87585?

CVE-2026-87585 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.28% probability of exploitation.

Which products are affected by CVE-2026-87585?

Affected products include Google Chrome.

How do I fix CVE-2026-87585?

Upgrade affected software to a fixed version, for example Google Chrome 153.0.8010.36 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-87585 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.