Secuno
ENNL
Book demo

CVE-2026-13883

Google Chrome type confusion

9.6 CRITICALEPSS 0.41%
  1. Published30 Jun 2026

Description

Type Confusion in ANGLE in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)

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< 150.0.7871.46

Remediation

Fixed in
Google Chrome≥ 150.0.7871.46

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1064338.8
Improper state management in MongoDB libmongocrypt can cause provider-specific data to…
CVE-2026-1064469.8
Handlebars provides the power necessary to let users build semantic templates. From…
CVE-2026-1063748.8
Type confusion in V8 in Google Chrome prior to 155.0.8059.39 allowed a remote attacker…
CVE-2026-1063418.8
Type confusion in V8 in Google Chrome prior to 155.0.8059.39 allowed a remote attacker…
CVE-2026-1062938.3
Type confusion in ANGLE in Google Chrome prior to 155.0.8059.39 allowed a remote…
CVE-2026-1062408.8
Type confusion in V8 in Google Chrome prior to 155.0.8059.39 allowed a remote attacker…

Frequently asked

Is CVE-2026-13883 being actively exploited?

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

How severe is CVE-2026-13883?

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

Which products are affected by CVE-2026-13883?

Affected products include Google Chrome.

How do I fix CVE-2026-13883?

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

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-13883 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.