ChromeWeb browser · Google
CVE-2026-14103
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUse after free in SSL in Google Chrome on ChromeOS prior to 150.0.7871.47 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Low)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUse-after-free vulnerability in the SSL component of Google Chrome on ChromeOS prior to version 150.0.7871.47. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, causing the browser to access freed memory and potentially leak sensitive information from the process memory space.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 150.0.7871.47CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify ChromeOS is the operating systemCheck the OS by looking at system information or running 'cat /etc/os-release' or checking the About ChromeOS section in SettingsAffected if Running ChromeOS as the operating system
-
Confirm Google Chrome browser is installedOpen Chrome and navigate to chrome://version or check the Chrome app in the app launcherAffected if Google Chrome browser is installed on the system
-
Determine the installed Chrome versionIn Chrome, type 'chrome://version' in the address bar and look at the 'Chrome' line which shows the version number (e.g., 150.0.7871.0)Affected if The displayed version number is present
-
Compare version against the affected rangeCompare your installed version number to the affected range: any version less than 150.0.7871.47 is vulnerableAffected if The installed version is lower than 150.0.7871.47 (for example, 150.0.7871.0 or 149.x.x.x)
-
Confirm SSL component is in useThe SSL component is enabled by default in Chrome for all HTTPS connections; no manual configuration needed - just verify Chrome is used for web browsingAffected if Google Chrome is used for web browsing with HTTPS sites (which is the default behavior)
The user is affected if Google Chrome on ChromeOS is installed and the installed version is lower than 150.0.7871.47.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped150.0.7871.47
Update Google Chrome on ChromeOS to version 150.0.7871.47 or later to patch the vulnerability.
150.0.7871.47
- Open Chrome browser on ChromeOS
- Click the three-dot menu in the top-right corner
- Select 'Settings' from the dropdown menu
- Click 'About Chrome' in the left sidebar
- Chrome will automatically check for updates; if version 150.0.7871.47 or later is available, click 'Update Chrome'
- Restart the browser after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14103 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14103 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data