CyberSecBulletin
CVE-2026-14036NVD status: Analyzed

Chrome: Client-Side Enforcement of Server-Side Security

Published Updated By the CyberSecBulletin desk

CVE-2026-14036 is a high-severity client-side enforcement of server-side security vulnerability in Chrome from Google, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 150.0.7871.47 as the first without the flaw, so updating Chrome to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.34% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Chrome to 150.0.7871.47 or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
  3. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
GoogleChrome150.0.7871.47 up to, but not including, 150.0.7871.47150.0.7871.47

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CISA (ADP).

Official description

Insufficient policy enforcement in Bluetooth in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Low)

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Client-Side Enforcement of Server-Side Security

The product includes a server that relies on the client to implement a protection mechanism that is intended to protect the server.

How developers prevent this class of flaw

  • If some degree of trust is required between the two entities, then use integrity checking and strong authentication to ensure that the inputs are coming from a trusted source. Design the product so that this trust is managed in a centralized fashion, especially if there are complex or numerous communication channels, in order to reduce the risks that the implementer will mistakenly omit a check in a single code path.

More Client-Side Enforcement of Server-Side Security vulnerabilities (CWE-602)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other references

Other vulnerabilities in Chrome

All Chrome vulnerabilities

Recent Client-Side Enforcement of Server-Side Security vulnerabilities

Spotted an error? Tell us.