# CVE-2026-14103: Google Chrome on ChromeOS use after free in SSL

Source: https://junglewise.ai/threats/cve-2026-14103-google-chrome-on-chromeos-use-after-free-in-ssl  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-30. Updated: 2026-07-01  
License: CC BY 4.0 with a link back

CVE-2026-14103 · Severity: info · CVSS 0 · Published 2026-06-30

A vulnerability exists in the SSL component of Google Chrome on ChromeOS. An attacker could use a specially crafted website to access sensitive information stored in the computer's memory. This could lead to the exposure of private data from other open tabs or browser processes.

Technologies: [Google ChromeOS](https://junglewise.ai/threats/technologies/chromeos). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-14103 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-14103 being exploited in the wild.

**How severe is CVE-2026-14103?** Informational severity, with a CVSS score of 0, published 30 June 2026.

**Which products and versions are affected?** Google ChromeOS prior to 150.0.7871.47.

**Is there a fix for CVE-2026-14103?** A patch was published on 2026-06-30. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-14103 attacked?** It is attacked over the network, in an operating system.

**Am I affected by CVE-2026-14103?** Check whether you run Google ChromeOS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A use-after-free (UAF) vulnerability exists within the SSL implementation of Google Chrome on ChromeOS. The flaw is triggered when the browser improperly manages memory objects during SSL operations, specifically when processing a maliciously crafted HTML page. A remote, unauthenticated attacker can exploit this condition to perform an out-of-bounds read of the browser's process memory. This can result in the disclosure of sensitive information, such as session tokens or other private data residing in memory. The issue is fixed in ChromeOS version 150.0.7871.47.

## Affected products

- Google ChromeOS prior to 150.0.7871.47

## Timeline

- 2026-06-30: disclosed
- 2026-06-30: patched

## References

- [https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html](https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html)
- [https://issues.chromium.org/issues/513465245](https://issues.chromium.org/issues/513465245)

## Related threats

- [Google ChromeOS heap buffer overflow in Color component](https://junglewise.ai/threats/cve-2026-17680-google-chromeos-heap-buffer-overflow-in-color-component)
- [Google ChromeOS uninitialized use in Dawn](https://junglewise.ai/threats/cve-2026-14421-google-chromeos-uninitialized-use-in-dawn)
- [Google ChromeOS out of bounds read in CameraCapture](https://junglewise.ai/threats/cve-2026-14090-google-chromeos-out-of-bounds-read-in-cameracapture)
- [Google Chrome on ChromeOS Information Disclosure in Views](https://junglewise.ai/threats/cve-2026-14062-google-chrome-on-chromeos-information-disclosure-in-views)
- [Google ChromeOS UI spoofing in Media UI](https://junglewise.ai/threats/cve-2026-13986-google-chromeos-ui-spoofing-in-media-ui)