Google Chrome authorization bypass in Chromoting
- Exploited
- No known exploitation
- Fix
- Fixed in 157.0.8103.38
- Who is exposed
- Not reported
Summary
Google Chrome has an incorrect authorization flaw in its Chromoting feature that lets an attacker bypass system access restrictions by using a local program. The CVSS vector indicates it can be reached remotely without logging in or any user action, though the description describes the attacker as local.
Written by a model
Original description
Incorrect authorization in Chromoting in Google Chrome prior to 157.0.8103.38 allowed a local attacker to bypass system access restrictions via a local program. (Chromium security severity: Low)
What to do
Upgrade to a fixed version: 157.0.8103.38.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-121157 (Incorrect authorization in Chromoting in Google Chrome prior to 157.0.8103.38 allowed a local attacker to bypass system access…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-121157 (entry last updated 2026-11-09):
Affected:
- Google Chrome: from 157.0.8103.38, fixed in 157.0.8103.38
Fixed versions: 157.0.8103.38.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-121157 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121157 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html
- https://issues.chromium.org/issues/533070896
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-121157
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121157"}.Affected versions
- Google ChromeFrom 157.0.8103.38 · fixed in 157.0.8103.38
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach20/20Affects Google Chrome (software on nearly every server, desktop or phone)
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 95 if added to CISA KEV
- Would score about 90 if CISA's SSVC rates exploitation active
- Would score about 55 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now6 days
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
- Posted on X by cve.now
Public exploit activity
- EPSS: 0.28%
- Posted on X by cve.now Nov 9
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-121157 |
| Record | NVD · CVE-2026-121157 |
| Other links 2 | |
| Link | chromereleases.googleblog.com · 2026/11/stable-channel-update-for-desktop.html |
| Link | issues.chromium.org · issues/533070896 |
Questions about CVE-2026-121157
Is CVE-2026-121157 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-121157?
Chrome: from 157.0.8103.38 before 157.0.8103.38.
Source: cve.now feed data
How do I fix CVE-2026-121157?
Upgrade to a fixed version: 157.0.8103.38.
Source: cve.now feed data
Why is it rated 9.8 Critical?
CVSS 9.8 scores the worst case. Chrome rates it Low.
Related
- CVE-2026-131037!MISSING CAUSE! in Chromoting in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to potentially execute arbitrary code…
- CVE-2026-131001Buffer overflow in Video in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to execute arbitrary code inside the sandbox…
- CVE-2026-130950Type confusion in V8 in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to execute arbitrary code inside the sandbox via a…
- CVE-2026-131005Use after free in DevTools in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to execute arbitrary code inside the sandbox…
- CVE-2026-130918Use after free in Views in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to execute…
- CVE-2026-130919Race condition in Printing in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to…
No corrections so far. Something wrong on this page? Report an error.