CVE-2026-113078 in the critical feed json
Race condition in Compositing in Google Chrome prior to 156.0.8078.47 allowed a remote attacker who had compromised the renderer process to…
published 20d ago modified 6d ago also EUVD-2026-105506
- cvss
- 9.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
Race condition in Compositing in Google Chrome prior to 156.0.8078.47 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
Patch / fix
- google chrome 156.0.8078.47
- chromium Debian 12 156.0.8078.47-1~deb12u1
- chromium Debian 13 156.0.8078.47-1~deb13u1
- chromium Debian 14 156.0.8078.47-1
debian advisories DEBIAN-CVE-2026-113078
- chromium openSUSE Leap 16.0 156.0.8078.47-bp160.1.1
- chromium openSUSE Tumbleweed 156.0.8078.47-1.1
opensuse advisories openSUSE-SU-2026:22185-1openSUSE-SU-2026:12234-1
Is CVE-2026-113078 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-113078 updated cvss 6.5
chromium-browser: Race condition in Compositing
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 20d ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
| CNA | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
- Technology feeds
References
-
chromereleases.googleblog.com
/2026/10/stable-channel-update-for-desktop_02018666648.html
release-notes, vendor-advisory
-
issues.chromium.org
/issues/499520020
issue-tracking
Sources
- CVE List CVE-2026-113078
- NVD CVE-2026-113078
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.