Secuno
ENNL
Book demo

CVE-2026-103630

Google Chrome remote code execution

9.6 CRITICALEPSS 0.33%
  1. Published2 Oct 2026

Description

Use after free in FedCM in Google Chrome prior to 154.0.8037.97 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

CVSS 3.1 breakdown

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

Affected products

Google Chrome< 154.0.8037.97

Remediation

Fixed in
Google Chrome≥ 154.0.8037.97

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-859658.0
Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7…
CVE-2026-57599.8
A double free and use-after-free vulnerability in the RdbLoadDeletedNodes function of…
CVE-2026-1071838.1
llama.cpp before b11393 contains a use-after-free and double free vulnerability in…
CVE-2026-553309.8
In BluetoothCccHandlerCallbackImpl of bluetooth_ccc.cc, there is a possible…
CVE-2026-1064238.8
Use after free in Media in Google Chrome prior to 155.0.8059.39 allowed a remote…
CVE-2026-1064218.8
Use after free in PDF in Google Chrome prior to 155.0.8059.39 allowed a remote attacker…

Frequently asked

Is CVE-2026-103630 being actively exploited?

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

How severe is CVE-2026-103630?

CVE-2026-103630 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 0.33% probability of exploitation.

Which products are affected by CVE-2026-103630?

Affected products include Google Chrome.

How do I fix CVE-2026-103630?

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

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-103630 against the real software inventory on every managed device, as each hourly inventory arrives. 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

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

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