CVSS 3.1
8.8 highCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HHigh (8.8) in google chrome. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExplain CVE-2026-126847 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126847?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126847?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-126847 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, 14 | chromium | no fix listed | DEBIAN-CVE-2026-126847 |
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 Important.
Red Hat Product Security rates this flaw as Important because successful exploitation allows an unauthenticated remote attacker to achieve arbitrary code execution within the browser's isolated renderer environment. The vulnerability requires user interaction, specifically convincing a user to process malicious web content in Chromium. While the flaw poses a significant integrity and confidentiality threat to the browser session, the impact is constrained by Chromium's operating system sandbox, preventing direct compromise of the underlying host unless chained with a separate privilege escalation or sandbox escape vulnerability.
Exercise operational precautions when browsing and ensure process isolation is strictly maintained:
1. Operational controls: Avoid visiting untrusted or unverified websites and do not open untrusted HTML files or embedded links from unverified sources.
2. Maintain sandboxing: Ensure Chromium is never launched with flags that disable security isolation (such as `--no-sandbox`). Operating system sandboxing is essential to restrict the blast radius of a compromised renderer process to the isolated browser sandbox.
3. Package removal: If web browsing functionality is not required on the system, remove the Chromium package using:
```
sudo dnf remove chromium
```
Caveats: Avoiding untrusted sites relies on user diligence and does not protect against compromised legitimate sites. Removing Chromium eliminates browser availability on the host, though server administration remains unaffected via terminal sessions.
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-126847.
Changes since this site first stored the record. The same for every record: /api/public/changes.