CVSS 3.1
3.1 lowCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:NLow (3.1) in google chrome. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:NExplain CVE-2026-126922 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126922?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126922?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126922 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Google Chrome | from 157.0.8103.78 before 157.0.8103.78 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | chromium | no fix listed | DEBIAN-CVE-2026-126922 |
| Debian | 14 | libskia, chromium | no fix listed | DEBIAN-CVE-2026-126922 |
From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.
Red Hat rates this Moderate.
This vulnerability is assessed as having a Moderate severity rather than Important because exploitation requires a pre-existing compromise of the browser's sandboxed renderer process. On Red Hat Enterprise Linux systems where chromium-browser is deployed, default multi-process sandboxing restricts the blast radius of renderer compromises from accessing the underlying operating system. Consequently, an attacker who induces a user to process malicious web content can only leak cross-origin memory within the browser session, without achieving arbitrary host code execution or elevated system privileges.
Avoid opening untrusted web pages or untrusted HTML documents in the browser. Ensure that chromium-browser is executed with its built-in sandbox and site isolation active, avoiding command-line options such as `--no-sandbox` or `--disable-site-isolation-trials`.
If chromium-browser is not strictly needed on the system, remove the package to eliminate the attack surface:
```
# dnf remove chromium-browser
```
Caveats: Restricting browser usage to trusted sites relies on operational discipline and may not be feasible in standard web workflows. Removing the package eliminates web browsing capabilities and may affect desktop applications or helper scripts that depend on chromium-browser.
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-126922.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
Changes since this site first stored the record. The same for every record: /api/public/changes.