No exploitation reportedFix available

CVE-2026-10886

Q: Is CVE-2026-10886 actively exploited?

Active exploitation of CVE-2026-10886 has not been confirmed. Its EPSS score was 6.2% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2026-10886?

CVE-2026-10886 has a CVSS v3 base score of 9.6 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H.

chromium-browser: Use after free in FileSystem

No exploitation reported by the sources we read.

Published2026-06-04
Fixed in149.0.7827.53
WeaknessCWE-416

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Use after free in FileSystem in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

Timeline

dates in UTC

2026-06-0423:16CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-10886?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-10886?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Google chromeversion to verify

Branch	Affected	Fixed in	Source
149.0	< 149.0.7827.53	149.0.7827.53	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

CVE-2026-10886 Red Hat Product Security
chromium-browser: Use after free in FileSystem

Full record on NVD

Fix

Update Google chrome to 149.0.7827.53

Advisories and patches

chromereleases.googleblog.comRelease Notes · Vendor Advisory

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVE recordread 2026-10-23
CISA-ADPSSVC decisionnone2026-06-05
OpenCVESSVC decisionnone—
CISA-ADPCVSS 3.19.62026-06-05
CNAweakness (CWE)CWE-416read 2026-10-23
FIRST EPSSEPSS score6.2 %2026-10-22
Microsoft MSRCadvisory—

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Published: 2026-06-04
Last Modified: 2026-07-22
NVD status: Analyzed
MSRC Title: Chromium: CVE-2026-10886 Use after free in FileSystem

Frequently asked questions

What is CVE-2026-10886?

Use after free in FileSystem in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

Is CVE-2026-10886 actively exploited?

Active exploitation of CVE-2026-10886 has not been confirmed. Its EPSS score was 6.2% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-10886?

CVE-2026-10886 has a CVSS v3 base score of 9.6 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H.

Running chromium-browser? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database