MEDIUM 6.5

CVE-2026-14381: Chrome WebAppInstalls UI Spoofing Vulnerability (v150)

Google Chrome versions before 150.0.7871.46 contain a flaw in the WebAppInstalls security UI that allows attackers to deceive users through carefully crafted web pages. An attacker can make Chrome's security indicators or install prompts appear fake, potentially tricking users into installing malicious web applications or granting unintended permissions. The vulnerability requires user interaction to exploit but poses a real risk because users rely on Chrome's visual cues to make trust decisions.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Weaknesses (CWE)
CWE-290, CWE-451
Affected products
1 configuration(s)
Published / Modified
2026-07-01 / 2026-07-02

NVD description (verbatim)

Incorrect security UI in WebAppInstalls in Google Chrome prior to 150.0.7871.46 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-14381 is a UI spoofing vulnerability affecting Chrome's WebAppInstalls feature. The root cause stems from incorrect security UI rendering, classified under CWE-290 (Improper Input Validation) and CWE-451 (User Interface (UI) Misrepresentation of Critical Information). An attacker crafts malicious HTML that exploits how Chrome renders or displays security-related UI elements during the web app installation flow. The attack vector is network-based with low complexity; the user must interact with the malicious page (e.g., click an install prompt or button) for the spoofing to take effect. The vulnerability carries a CVSS 3.1 score of 6.5 (Medium severity) with high integrity impact but no confidentiality or availability impact.

Business impact

This vulnerability primarily threatens user trust and application integrity. Attackers could trick employees or customers into installing counterfeit web apps that mimic legitimate services, potentially leading to credential theft, data exfiltration, or further social engineering. For enterprises deploying Progressive Web Apps (PWAs) or relying on web-based application distribution, this increases the attack surface for internal users. The reputational risk is secondary but meaningful: if users are deceived into installing fake apps via spoofed Chrome prompts, confidence in the organization's digital distribution channel erodes.

Affected systems

Google Chrome versions prior to version 150.0.7871.46 are affected. This includes all supported and legacy Chrome releases that fall below this threshold across Windows, macOS, Linux, Android, and iOS platforms. Users who have auto-update enabled should receive the patch automatically; those on manual update cycles must upgrade explicitly. Enterprise deployments pinned to older Chrome versions remain vulnerable until updated. Chrome-based browsers and derivatives that ship the affected Chromium code (before the fix was integrated upstream) may also be impacted.

Exploitability

Exploitation requires delivery of a specially crafted HTML page to the victim, typically via phishing, malvertising, or a compromised web server. The attacker cannot exploit the vulnerability silently; the user must interact with the spoofed UI (e.g., proceed with an install action). This human element raises the bar for mass exploitation but does not meaningfully reduce risk in targeted scenarios. No public exploit code or active in-the-wild attacks are documented in the KEV catalog. However, the attack requires no special privileges, can be launched over the network, and relies only on a user's normal browsing behavior, making it a moderate-difficulty social engineering vector.

Remediation

Update Google Chrome to version 150.0.7871.46 or later. For Windows and macOS, users can navigate to Chrome > Settings > About to trigger automatic update checks. Linux users should update via their package manager. Enterprise administrators should verify patch deployment across managed Chrome instances. For organizations using Chrome Fleet Management or similar tools, centralized rollout is recommended. Verify successful upgrade by confirming the version number in chrome://version.

Patch guidance

Apply Chrome version 150.0.7871.46 or any subsequent release. No interim mitigations are necessary once the patch is deployed. If your environment has Chrome update management policies, ensure policies permit this update or manually schedule a deployment window. For devices on auto-update, no action is typically required beyond standard browser restart workflows. Confirm patch application by auditing version telemetry across your managed Chrome fleet.

Detection guidance

Monitor for suspicious WebAppInstalls flows in user sessions—look for unexpected or out-of-band web app installation prompts, especially those requesting elevated permissions. Endpoint Detection and Response (EDR) tools can track chrome.exe process behavior during PWA install operations. Network-layer detection is limited since the exploit uses legitimate Chrome functionality; focus on user reports of fake install prompts or suspicious web app installations. Encourage users to verify app sources before approving install prompts and to report visually unusual security dialogs.

Why prioritize this

Although marked as Medium severity, this vulnerability should be prioritized for rapid patching in organizations where users regularly interact with web applications or PWAs. The UI spoofing mechanism is particularly effective in enterprise environments relying on web-based SaaS tools, as attackers can craft prompts that closely mimic legitimate corporate application distribution. The requirement for user interaction does not significantly lower risk in social engineering-heavy attack scenarios. Early patching reduces the window in which employees can be deceived.

Risk score, explained

The CVSS 6.5 (Medium) score reflects high integrity impact (attackers can trick users into installing fake apps) balanced against the user interaction requirement and network-based attack vector. Confidentiality and availability are not directly impacted, which prevents a higher score. However, the practical risk is elevated in environments with security-conscious users or highly targeted phishing campaigns, as the spoofed UI is difficult for non-technical users to distinguish from legitimate Chrome prompts.

Frequently asked questions

Do I need to do anything if I have Chrome set to auto-update?

Chrome auto-updates in the background on most platforms. You may need to restart your browser or device for the update to take effect. Check chrome://version to confirm you're running 150.0.7871.46 or later. If your version is older, restart Chrome or check for pending updates in Settings > About.

Can this vulnerability be exploited without the user knowing?

No. The exploit requires user interaction—typically clicking on a malicious install prompt or interacting with a spoofed UI element on a web page. A user cannot be passively compromised just by visiting a page. However, if the spoofed prompt is convincing, users may not realize they are installing an untrusted app.

Are Chrome Enterprise or Chromebook users affected?

Yes. All Chrome instances before version 150.0.7871.46 are vulnerable. Enterprise administrators should use Chrome Fleet Management or MDM policies to enforce the patch. Chromebook administrators should verify that ChromeOS auto-update policies are current and that devices are receiving the latest Chrome release.

What should I look for if I suspect I clicked on a malicious install prompt?

Check your system's installed apps or browser extensions for unfamiliar entries. Review Chrome's app list in chrome://apps and chrome://extensions. Run a malware scan if you noticed unusual behavior. If the fake app requested access to sensitive data (passwords, photos), consider rotating credentials and monitoring your accounts for suspicious activity.

This analysis is based on official CVE and Chromium security data current as of July 2026. Patch version numbers and severity assessments derive from Google's security advisory. Organizations should verify patch applicability in their environment and consult official vendor documentation before deployment. No exploit proof-of-concept code is provided. This vulnerability is not listed in CISA's KEV catalog, indicating no evidence of active in-the-wild exploitation at the time of publication, but organizations should not use this as justification to delay patching. Source: NVD (public-domain), retrieved 2026-08-10. Analysis generated by SEC.co (claude-haiku-4-5).