Chrome: Heap-based Buffer Overflow (CVE-2026-121156)
Published Sources: BSI
What is affected, what to do
Buffer overflow in Dawn in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical)
The available sources name no fixed version. Check the vendor guidance in the references below.
Conflicting version data — version display is hidden until the data is resolved.
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.6
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
9.6
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: BSI
0.5 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 41.7
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 76.06 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 9.6 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.6
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.5 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 41.7
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 4 November 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-122
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
Buffer overflow in Dawn in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical)
Source: BSI WID Portal
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Chrome |
|
| |
| chrome |
|
|
From bundled advisories, not CVE-specific (1)
Product list of a bundled advisory that does not state which product this CVE affects.
| Affected versions | Fixed in | ||
|---|---|---|---|
| chrome |
|
|
Vendors and products
Weakness classes (CWE)
CWE-122Heap-based Buffer Overflow
Variant
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Entry at MITRE CWE-122
References & sources
- chromereleases.googleblog.com2026/11/stable-channel-update-for-desktop.htmlRelease notes, Vendor advisory
- issues.chromium.orgissues/574351803Permissions required
- issues.chromium.orgissues/561994040Permissions required
- issues.chromium.orgissues/565505280
- issues.chromium.orgissues/553652456Permissions required
- issues.chromium.orgissues/574791491Permissions required
- issues.chromium.orgissues/574922421Permissions required
- issues.chromium.orgissues/550489336
- issues.chromium.orgissues/577378379Permissions required
- issues.chromium.orgissues/574021176Permissions required
- issues.chromium.orgissues/492163889Permissions required
- issues.chromium.orgissues/571059182Permissions required
- issues.chromium.orgissues/573387527Permissions required
- issues.chromium.orgissues/568999538Permissions required
- issues.chromium.orgissues/568818122Permissions required
- issues.chromium.orgissues/574376940
- issues.chromium.orgissues/500171457Permissions required
- issues.chromium.orgissues/550245671Permissions required
- issues.chromium.orgissues/571058818Permissions required
- issues.chromium.orgissues/570026368Permissions required
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Initial analysis by NVDNVD
Newly listed as affected:- Google Chrome (before 157.0.8103.38)
Show 3 original changes
Individual changes of this event as published by NVD Type Action Before After Product configuration added —OR *cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* versions up to (excluding) 157.0.8103.38Reference type added —Chrome: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html Types: Release Notes, Vendor AdvisoryReference type added —Chrome: https://issues.chromium.org/issues/567735302 Types: Permissions RequiredSource identifier: nvd@nist.gov
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After SSVC assessment removed {"id":"CVE-2026-121156","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-03T00:00:00+00:00"}—SSVC assessment added —{"id":"CVE-2026-121156","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-04T04:56:33.292905Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After SSVC assessment removed {"id":"CVE-2026-121156","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-03T21:23:38.157233Z"}—SSVC assessment added —{"id":"CVE-2026-121156","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-03T00:00:00+00:00"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Record modifiedCISA ADP
CVSS V3.1: AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CISA assessment (SSVC): exploitation: none known, automatable: no
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After CVSS added —AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HSSVC assessment added —{"id":"CVE-2026-121156","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-03T21:23:38.157233Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedGoogle Chrome
Weakness type: CWE-122
Description added or changed
Show 5 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —Buffer overflow in Dawn in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical)Weakness type (CWE) added —CWE-122Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/121xxx/CVE-2026-121156.json">CVE-2026-121156</a>Reference added —https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.htmlReference added —https://issues.chromium.org/issues/567735302Source identifier: chrome-cve-admin@google.com
Linked CVEs
| Critical | CVE-2026-121257 | Google Chrome: Use After Free | 9.6 | — |
| High | CVE-2026-121256 | Google Chrome: Operation on a Resource after Expiration or Release | 8.3 | — |
| Medium | CVE-2026-121255 | Google Chrome: Incorrect Authorization | 6.5 | — |
| Medium | CVE-2026-121254 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 6.5 | — |
| Not rated | CVE-2026-121253 | Google Chrome: Missing Authorization | — | — |
| High | CVE-2026-121252 | Google Chrome: Incorrect Authorization | 8.8 | — |
| High | CVE-2026-121251 | Google Chrome: Missing Authorization | 8.8 | — |
| Critical | CVE-2026-121250 | Google Chrome: Use After Free | 9.6 | — |
| Critical | CVE-2026-121249 | Google Chrome: Stack-based Buffer Overflow | 9.6 | — |
| Not rated | CVE-2026-121248 | Google Chrome: Incorrect Authorization | — | — |
| Critical | CVE-2026-121247 | Google Chrome: Heap-based Buffer Overflow | 9.6 | — |
| Critical | CVE-2026-121246 | Google Chrome: Use After Free | 9.6 | — |
| Medium | CVE-2026-121245 | Google Chrome: Time-of-check Time-of-use (TOCTOU) Race Condition | 5.3 | — |
| Medium | CVE-2026-121244 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| Medium | CVE-2026-121243 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 6.5 | — |
| Not rated | CVE-2026-121242 | Google Chrome: Improper Input Validation | — | — |
| Critical | CVE-2026-121241 | Google Chrome: Use After Free | 9.6 | — |
| Not rated | CVE-2026-121240 | Google Chrome: Improper Input Validation | — | — |
| Medium | CVE-2026-121239 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 6.5 | — |
| High | CVE-2026-121238 | Google Chrome: Use After Free | 8.8 | — |
| Not rated | CVE-2026-121237 | Google Chrome: Improper Check for Unusual or Exceptional Conditions | — | — |
| High | CVE-2026-121236 | Google Chrome: Improper Input Validation | 8.8 | — |
| Medium | CVE-2026-121235 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 6.5 | — |
| Critical | CVE-2026-121234 | Google Chrome: Execution with Unnecessary Privileges | 9.6 | — |
Show 189 more CVEs
| High | CVE-2026-121233 | Google Chrome: Type Confusion | 8.8 | — |
| Medium | CVE-2026-121232 | Google Chrome: Incorrect Authorization | 5.1 | — |
| Not rated | CVE-2026-121231 | Google Chrome: Incorrect Authorization | — | — |
| High | CVE-2026-121230 | Google Chrome: Race Condition | 8.3 | — |
| Critical | CVE-2026-121229 | Google Chrome: Improper Restriction of Operations within the Bounds of a Memory Buffer | 9.6 | — |
| High | CVE-2026-121228 | Google Chrome: Type Confusion | 8.8 | — |
| Not rated | CVE-2026-121227 | Google Chrome: Use of Uninitialized Resource | — | — |
| High | CVE-2026-121226 | Google Chrome: Type Confusion | 8.8 | — |
| Not rated | CVE-2026-121225 | Google Chrome: Incorrect Authorization | — | — |
| High | CVE-2026-121224 | Google Chrome: Link Following | 8.1 | — |
| Not rated | CVE-2026-121223 | Google Chrome: Observable Discrepancy | — | — |
| High | CVE-2026-121222 | Google Chrome: Incorrect Authorization | 8.8 | — |
| High | CVE-2026-121221 | Google Chrome: Type Confusion | 8.8 | — |
| Not rated | CVE-2026-121220 | Google Chrome: Incorrect Authorization | — | — |
| High | CVE-2026-121219 | Google Chrome: Integer Overflow or Wraparound | 8.3 | — |
| High | CVE-2026-121218 | Google Chrome: Type Confusion | 8.8 | — |
| High | CVE-2026-121217 | Google Chrome: Use After Free | 7.5 | — |
| Medium | CVE-2026-121216 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| Medium | CVE-2026-121215 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| Critical | CVE-2026-121214 | Google Chrome: Use After Free | 9.6 | — |
| Medium | CVE-2026-121213 | Google Chrome: Use of Uninitialized Resource | 6.5 | — |
| High | CVE-2026-121212 | Google Chrome: Incorrect Authorization | 8.8 | — |
| High | CVE-2026-121211 | Google Chrome: Use After Free | 8.3 | — |
| High | CVE-2026-121210 | Google Chrome: Type Confusion | 8.8 | — |
| Not rated | CVE-2026-121209 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | — | — |
| High | CVE-2026-121208 | Google Chrome: Out-of-bounds Read | 8.8 | — |
| Not rated | CVE-2026-121207 | Google Chrome: Use of Uninitialized Resource | — | — |
| Medium | CVE-2026-121206 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| High | CVE-2026-121205 | Google Chrome: Incorrect Authorization | 8.8 | — |
| High | CVE-2026-121204 | Google Chrome: Incomplete Cleanup | 8.8 | — |
| High | CVE-2026-121203 | Google Chrome: Use After Free | 8.8 | — |
| Critical | CVE-2026-121202 | Google Chrome: Use After Free | 9.6 | — |
| High | CVE-2026-121201 | Google Chrome: Use After Free | 8.8 | — |
| Critical | CVE-2026-121200 | Google Chrome: Use of Incorrectly-Resolved Name or Reference | 9.6 | — |
| Medium | CVE-2026-121199 | Google Chrome: Missing Authorization | 5.5 | — |
| High | CVE-2026-121198 | Google Chrome: Confused Deputy | 8.8 | — |
| Not rated | CVE-2026-121197 | Google Chrome: Out-of-bounds Read | — | — |
| Not rated | CVE-2026-121196 | Google Chrome: Execution with Unnecessary Privileges | — | — |
| High | CVE-2026-121195 | Google Chrome: Incorrect Authorization | 8.8 | — |
| Medium | CVE-2026-121194 | Google Chrome: Missing Authorization | 5.3 | — |
| Not rated | CVE-2026-121193 | Google Chrome: Incorrect Authorization | — | — |
| Not rated | CVE-2026-121190 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | — | — |
| Critical | CVE-2026-121189 | Google Chrome: Use After Free | 9.6 | — |
| High | CVE-2026-121188 | Google Chrome: Use After Free | 8.8 | — |
| Medium | CVE-2026-121187 | Google Chrome: Observable Discrepancy | 5.3 | — |
| Medium | CVE-2026-121186 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| Critical | CVE-2026-121185 | Google Chrome: Use After Free | 9.6 | — |
| High | CVE-2026-121184 | Google Chrome: Out-of-bounds Read | 8.8 | — |
| High | CVE-2026-121183 | Google Chrome: Incorrect Authorization | 8.3 | — |
| High | CVE-2026-121182 | Google Chrome: Use After Free | 8.8 | — |
| High | CVE-2026-121181 | Google Chrome: Use After Free | 8.8 | — |
| High | CVE-2026-121180 | Google Chrome: Heap-based Buffer Overflow | 8.8 | — |
| High | CVE-2026-121179 | Google Chrome: Use After Free | 8.8 | — |
| High | CVE-2026-121178 | Google Chrome: Use After Free | 8.3 | — |
| Medium | CVE-2026-121177 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| Medium | CVE-2026-121176 | Google Chrome: Use of Uninitialized Resource | 6.5 | — |
| Not rated | CVE-2026-121175 | Google Chrome: Exposure of Resource to Wrong Sphere | — | — |
| High | CVE-2026-121174 | Google Chrome: Missing Authorization | 8.8 | — |
| Not rated | CVE-2026-121173 | Google Chrome: Use of Uninitialized Resource | — | — |
| Medium | CVE-2026-121172 | Google Chrome: Incorrect Authorization | 5.4 | — |
| High | CVE-2026-121171 | Google Chrome: Confused Deputy | 8.8 | — |
| High | CVE-2026-121170 | Google Chrome: Improper Control of Dynamically-Managed Code Resources | 8.8 | — |
| Not rated | CVE-2026-121169 | Google Chrome: Missing Authorization | — | — |
| High | CVE-2026-121168 | Google Chrome: Exposure of Resource to Wrong Sphere | 8.8 | — |
| Not rated | CVE-2026-121167 | Google Chrome: Incorrect Authorization | — | — |
| High | CVE-2026-121166 | Google Chrome: Type Confusion | 8.8 | — |
| Medium | CVE-2026-121165 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| Not rated | CVE-2026-121164 | Google Chrome: Incorrect Authorization | — | — |
| High | CVE-2026-121163 | Google Chrome: Improper Input Validation | 8.3 | — |
| Medium | CVE-2026-121162 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| Medium | CVE-2026-121161 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 6.5 | — |
| Not rated | CVE-2026-121160 | Google Chrome: Out-of-bounds Read | — | — |
| Not rated | CVE-2026-121159 | Google Chrome: Incorrect Authorization | — | — |
| Medium | CVE-2026-121158 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 6.5 | — |
| Not rated | CVE-2026-121157 | Google Chrome: Incorrect Authorization | — | — |
| Critical | CVE-2026-121156 | Google Chrome: Heap-based Buffer Overflow | 9.6 | — |
| Critical | CVE-2026-121148 | Google Chrome: Use After Free | 9.6 | — |
| Not rated | CVE-2026-121143 | Google Chrome: Use of Uninitialized Resource | — | — |
| Not rated | CVE-2026-121142 | Google Chrome: Incorrect Authorization | — | — |
| Medium | CVE-2026-121141 | Google Chrome: Improper Input Validation | 5.4 | — |
| High | CVE-2026-121140 | Google Chrome: Out-of-bounds Read | 8.3 | — |
| Medium | CVE-2026-121138 | Google Chrome: Observable Discrepancy | 6.5 | — |
| High | CVE-2026-121137 | Google Chrome: Type Confusion | 8.8 | — |
| Not rated | CVE-2026-121136 | Google Chrome: Missing Authorization | — | — |
| High | CVE-2026-121135 | Google Chrome: Interpretation Conflict | 8.8 | — |
| High | CVE-2026-121134 | Google Chrome: Information Loss or Omission | 8.8 | — |
| High | CVE-2026-121133 | Google Chrome: Use of Incorrectly-Resolved Name or Reference | 8.1 | — |
| Medium | CVE-2026-121132 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 6.5 | — |
| Critical | CVE-2026-121131 | Google Chrome: Use After Free | 9.6 | — |
| Medium | CVE-2026-121130 | Google Chrome: Observable Discrepancy | 5.3 | — |
| High | CVE-2026-121129 | Google Chrome: Use After Free | 8.8 | — |
| High | CVE-2026-121128 | Google Chrome: Use After Free | 8.8 | — |
| High | CVE-2026-121127 | Google Chrome: Use After Free | 8.8 | — |
| Critical | CVE-2026-121126 | Google Chrome: Use After Free | 9.6 | — |
| Medium | CVE-2026-121125 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 5.3 | — |
| High | CVE-2026-121124 | Google Chrome: Improper Adherence to Coding Standards | 8.8 | — |
| High | CVE-2026-121123 | Google Chrome: Use After Free | 8.8 | — |
| Medium | CVE-2026-121122 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| Medium | CVE-2026-121121 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| High | CVE-2026-121120 | Google Chrome: Improper Input Validation | 8.8 | — |
| High | CVE-2026-121119 | Google Chrome: Use After Free | 8.8 | — |
| High | CVE-2026-121118 | Google Chrome: Use After Free | 8.8 | — |
| High | CVE-2026-121117 | Google Chrome: Use After Free | 8.8 | — |
| Medium | CVE-2026-121116 | Google Chrome: Missing Authorization | 5.3 | — |
| Not rated | CVE-2026-121115 | Google Chrome: Improper Input Validation | — | — |
| Critical | CVE-2026-121114 | Google Chrome: Use After Free | 9.6 | — |
| High | CVE-2026-121113 | Google Chrome: Heap-based Buffer Overflow | 8.8 | — |
| High | CVE-2026-121112 | Google Chrome: Out-of-bounds Read | 8.3 | — |
| Not rated | CVE-2026-121111 | Google Chrome: Incorrect Authorization | — | — |
| Medium | CVE-2026-121110 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| Not rated | CVE-2026-121109 | Google Chrome: Inadequate Encryption Strength | — | — |
| High | CVE-2026-121108 | Google Chrome: Confused Deputy | 8.8 | — |
| High | CVE-2026-121107 | Google Chrome: Incorrect Authorization | 8.8 | — |
| Medium | CVE-2026-121106 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 6.5 | — |
| Medium | CVE-2026-121105 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 6.5 | — |
| Critical | CVE-2026-121104 | Google Chrome: Incorrect Authorization | 9.6 | — |
| Not rated | CVE-2026-121103 | Google Chrome: Incorrect Authorization | — | — |
| High | CVE-2026-121102 | Google Chrome: Missing Authorization | 8.8 | — |
| Not rated | CVE-2026-121101 | Google Chrome: Missing Authorization | — | — |
| High | CVE-2026-121100 | Google Chrome: Use After Free | 8.8 | — |
| Medium | CVE-2026-121099 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 6.5 | — |
| High | CVE-2026-121098 | Google Chrome: Improper Check for Unusual or Exceptional Conditions | 8.3 | — |
| High | CVE-2026-121097 | Google Chrome: Use After Free | 8.8 | — |
| Not rated | CVE-2026-121096 | Google Chrome: Incomplete Cleanup | — | — |
| Not rated | CVE-2026-121095 | Google Chrome: Use of Uninitialized Resource | — | — |
| High | CVE-2026-121094 | Google Chrome: Type Confusion | 8.8 | — |
| Not rated | CVE-2026-121093 | Google Chrome: Out-of-bounds Read | — | — |
| High | CVE-2026-121092 | Google Chrome: Uncontrolled Recursion | 8.8 | — |
| Medium | CVE-2026-121091 | Google Chrome: Incorrect Authorization | 5.3 | — |
| High | CVE-2026-121090 | Google Chrome: Improper Privilege Management | 8.3 | — |
| Critical | CVE-2026-121089 | Google Chrome: Use After Free | 9.6 | — |
| Medium | CVE-2026-121088 | Google Chrome: Missing Authorization | 6.5 | — |
| High | CVE-2026-121087 | Google Chrome: Improper Input Validation | 8.8 | — |
| Critical | CVE-2026-121086 | Google Chrome: Heap-based Buffer Overflow | 9.6 | — |
| Not rated | CVE-2026-121085 | Google Chrome: Incorrect Authorization | — | — |
| High | CVE-2026-121084 | Google Chrome: Out-of-bounds Read | 8.3 | — |
| High | CVE-2026-121083 | Google Chrome: Use After Free | 8.8 | — |
| High | CVE-2026-121082 | Google Chrome: Type Confusion | 8.8 | — |
| Medium | CVE-2026-121081 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.9 | — |
| Medium | CVE-2026-121080 | Google Chrome: Use After Free | 4.3 | — |
| High | CVE-2026-121079 | Google Chrome: Race Condition | 8.8 | — |
| High | CVE-2026-121078 | Google Chrome: Type Confusion | 8.8 | — |
| Critical | CVE-2026-121077 | Google Chrome: Use After Free | 9.6 | — |
| Critical | CVE-2026-121076 | Google Chrome: Use After Free | 9.6 | — |
| Not rated | CVE-2026-121075 | Google Chrome: Missing Authorization | — | — |
| Critical | CVE-2026-121074 | Google Chrome: Improper Restriction of Operations within the Bounds of a Memory Buffer | 9.6 | — |
| Critical | CVE-2026-121073 | Google Chrome: Use After Free | 9.6 | — |
| Medium | CVE-2026-121072 | Google Chrome: Use of Uninitialized Resource | 6.5 | — |
| Critical | CVE-2026-121071 | Google Chrome: Incorrect Authorization | 9.6 | — |
| High | CVE-2026-121070 | Google Chrome: Use After Free | 8.8 | — |
| High | CVE-2026-121069 | Google Chrome: Use After Free | 8.8 | — |
| High | CVE-2026-121068 | Google Chrome: Type Confusion | 8.8 | — |
| Medium | CVE-2026-121067 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| Not rated | CVE-2026-121066 | Google Chrome: Incorrect Authorization | — | — |
| High | CVE-2026-121065 | Google Chrome: Incorrect Authorization | 8.8 | — |
| High | CVE-2026-121064 | Google Chrome: Improper Input Validation | 7.8 | — |
| Not rated | CVE-2026-121063 | Google Chrome: Incorrect Authorization | — | — |
| Not rated | CVE-2026-121062 | Google Chrome: Incorrect Authorization | — | — |
| High | CVE-2026-121061 | Google Chrome: Use After Free | 8.8 | — |
| Critical | CVE-2026-121060 | Google Chrome: Incorrect Authorization | 9.6 | — |
| Medium | CVE-2026-121059 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 6.5 | — |
| High | CVE-2026-121057 | Google Chrome: Type Confusion | 8.8 | — |
| Not rated | CVE-2026-121055 | Google Chrome: Incomplete Cleanup | — | — |
| High | CVE-2026-121054 | Google Chrome: Improper Check for Unusual or Exceptional Conditions | 8.8 | — |
| Medium | CVE-2026-121053 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| High | CVE-2026-121052 | Google Chrome: Use After Free | 8.8 | — |
| Not rated | CVE-2026-121051 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | — | — |
| High | CVE-2026-121050 | Google Chrome: Time-of-check Time-of-use (TOCTOU) Race Condition | 8.8 | — |
| Low | CVE-2026-121049 | Google Chrome: Out-of-bounds Read | 3.3 | — |
| High | CVE-2026-121048 | Google Chrome: Time-of-check Time-of-use (TOCTOU) Race Condition | 8.8 | — |
| High | CVE-2026-121047 | Google Chrome: Heap-based Buffer Overflow | 8.8 | — |
| Not rated | CVE-2026-121046 | Google Chrome: Incorrect Authorization | — | — |
| Medium | CVE-2026-121045 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| High | CVE-2026-121044 | Google Chrome: Use After Free | 8.8 | — |
| Medium | CVE-2026-121043 | Google Chrome: User Interface (UI) Misrepresentation of Critical Information | 5.4 | — |
| Not rated | CVE-2026-121042 | Google Chrome: Incorrect Authorization | — | — |
| Medium | CVE-2026-121041 | Google Chrome: Missing Authorization | 6.5 | — |
| Not rated | CVE-2026-121040 | Google Chrome: Incorrect Authorization | — | — |
| Medium | CVE-2026-121039 | Google Chrome: Incorrect Authorization | 5.3 | — |
| Medium | CVE-2026-121038 | Google Chrome: Exposure of Sensitive Information to an Unauthorized Actor | 6.5 | — |
| Critical | CVE-2026-121037 | Google Chrome: Out-of-bounds Write | 9.6 | — |
| High | CVE-2026-121036 | Google Chrome: Use After Free | 8.8 | — |
| Critical | CVE-2026-121035 | Google Chrome: Use After Free | 9.6 | — |
| Critical | CVE-2026-121034 | Google Chrome: Use After Free | 9.6 | — |
| Not rated | CVE-2026-121033 | Google Chrome: Use of Uninitialized Resource | — | — |
| Not rated | CVE-2026-121032 | Google Chrome: Out-of-bounds Read | — | — |
| Not rated | CVE-2026-121031 | Google Chrome: Missing Authorization | — | — |
| Critical | CVE-2026-121030 | Google Chrome: Incorrect Authorization | 9.6 | — |
| Not rated | CVE-2026-121029 | Google Chrome: Incorrect Authorization | — | — |
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-121156"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-121156.svg?lang=en" alt="CVE-2026-121156 – NEOSEC Intel" height="20"></a>