Incorrect authorization in Actor in Google Chrome on on Android prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to potentially bypass site isolation via a crafted HTML page. (Chromium security severity: Low)
CVE-2026-106199
MEDIUMCVSS · not yet scored5.4Trending — 5 sources updated this week
EchelonGraph scoreLOW confidence
Google's Chromium security team rated this Low in the advisory text — the exact wording is "(Chromium security severity: Low)". Chromium's CNA does not publish a CVSS vector, and NVD has not yet analysed this record, so there is no CVSS v3.1, v4.0 or v2.0 base score for it from any source. EchelonGraph publishes 5.4 (MEDIUM), derived from the VENDOR'S OWN SEVERITY BAND — not from a CVSS vector. That number is calibrated, not assumed: across 413 Chromium CVEs that NVD has since scored, a Chromium "Low" carried a median CVSS v3 base of 5.4. Note that Chromium's "Low" is not CVSS LOW: only 9 of 413 such CVEs were scored below 4.0 by NVD, and 71% landed in CVSS MEDIUM. Chromium's bands express Google's triage priority, not CVSS severity. This score is provisional and will be superseded the moment any source publishes a real CVSS base. Confidence: LOW.
Sources: vendor_prose:chromium
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- —
- Vendor severity
- LOWper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Low)
- EG Score
- 5.4MEDIUMlow confidence
- EG Risk
- 29EG Risk 29/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.2%
- EPSS %ILE
- 10th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 6, 2026
Last Modified
October 6, 2026
References (2)
- chrome-cve-admin@googlehttps://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html
- chrome-cve-admin@googlehttps://issues.chromium.org/issues/517703787
Vendor Advisories for CVE-2026-106199(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-07 23:47 UTCEPSS rescore
- 2026-10-07 22:09 UTCGHSA enrichment
- 2026-10-06 19:31 UTCNVD update
- 2026-10-06 18:57 UTCEG score recompute
- 2026-10-06 18:57 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-106199?
CVE-2026-106199 is a medium vulnerability published on October 6, 2026. Incorrect authorization in Actor in Google Chrome on on Android prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to potentially bypass site isolation via a crafted HTML page. (Chromium security severity: Low)
When was CVE-2026-106199 disclosed?
CVE-2026-106199 was first published on October 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-106199 actively exploited?
CVE-2026-106199 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-106199?
No fix for CVE-2026-106199 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-106199 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-106199
Is Your Infrastructure Affected by CVE-2026-106199?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.