Security Resilience

CVE-2026-95328

Google Chrome ≤ 154.0.8037.57

Published
29 September 2026
Modified
30 September 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS Score 0.0023 12th percentile
Risk Priority 49 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-95328 is a medium-severity Confused Deputy (CWE-441) vulnerability in Google Chrome. Its CVSS base score is 6.5 (Medium).

Operationally, ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-16 (Security and Privacy Attributes) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Confused deputy in Mobile in Google Chrome on on Android prior to 154.0.8037.57 allowed a local attacker leveraging social engineering to obtain sensitive information via a co-installed app. (Chromium security severity: Low)

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-106326Same product: Google Android
CVE-2026-106221Same product: Google Android
CVE-2026-106188Same product: Google Android
CVE-2026-9889Same product: Google Android
CVE-2026-9929Same product: Google Android
CVE-2026-15900Same product: Google Android
CVE-2026-17872Same product: Google Android
CVE-2023-1230Same product: Google Android
CVE-2026-11019Same product: Google Android
CVE-2026-10932Same product: Google Android

Affected Assets

google
chrome
≤ 154.0.8037.57

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Associating and preserving security attributes such as original source identity prevents the loss of provenance that creates the confused deputy.

Access enforcement directly stops a component from acting on forwarded requests without verifying original source authorizations.

Information flow enforcement requires preserving and checking source attributes before forwarding requests outside the trust boundary.

Boundary protection limits and inspects external forwarding, reducing the ability of an intermediary to act as an unintended proxy.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.5.15 only requires defining and documenting an access control policy plus requirements; it does not itself enforce rules or stop a confused-deputy proxy from being introduced or exploited.

blocks

A.5.16 governs identity lifecycle, uniqueness, accountability and timely removal to support proper access rights assignment; it has no bearing on preserving original request sources or stopping confused-deputy proxying when a product forwards an upstream request.

degrades

Explicit access-rights assignment can restrict the product’s ability to act as an unintended proxy for external actors.

degrades

Privileged-access controls limit the rights the product may exercise on behalf of upstream callers, mitigating confused-deputy abuse.

degrades

Network-security controls can enforce source validation and prevent the product from blindly proxying traffic to external actors.

blocks

Secure-SDLC practices include design reviews that detect and eliminate confused-deputy proxy patterns before deployment.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-441, a class-level weakness, and none of its children carries one either.

References