Security Resilience

CVE-2026-95295

Info Disclosure in Google Chrome ≤ 154.0.8037.57

Public PoCInfo Disclosure
Published
29 September 2026
Modified
01 October 2026
Patch / advisory
CVSS Score v3.1 4.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0013 2th percentile
Risk Priority 34 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-95295 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor (CWE-200) vulnerability in Google Chrome. Its CVSS base score is 4.6 (Medium).

Operationally, ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

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

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Information leak in Mobile in Google Chrome on on iOS prior to 154.0.8037.57 allowed a local attacker to leak sensitive information via physical access. (Chromium security severity: Medium)

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-18011Same product: Google Chrome
CVE-2026-9955Same product: Google Chrome
CVE-2026-106192Same product: Google Chrome
CVE-2026-87545Same product: Google Chrome
CVE-2026-113268Same product: Google Chrome
CVE-2023-1225Same product: Google Chrome
CVE-2026-11203Same product: Google Chrome
CVE-2026-17966Same product: Google Chrome
CVE-2026-17975Same product: Google Chrome
CVE-2026-17973Same product: Google Chrome

Affected Assets

google
chrome
≤ 154.0.8037.57

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Access enforcement directly stops unauthorized actors from obtaining sensitive information.

Information flow enforcement structurally prevents sensitive data from reaching unauthorized recipients.

Least privilege reduces the set of actors who can reach sensitive information.

Protection of information at rest prevents unauthorized exposure of stored sensitive data.

Transmission confidentiality mechanisms stop exposure of sensitive data on the wire.

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

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Penetration testing and vulnerability scanning are performed to discover unintended exposure of sensitive data resulting from misconfigurations or coding errors.

blocks

Restricting anonymous or unknown access and encrypting high-value information limits the exposure of sensitive data that would otherwise be obtainable by unauthorized actors.

blocks

By requiring removal or masking of sensitive operational data before it enters test environments, the control sharply reduces the chance that such data will be exposed to unauthorized actors who have access to those environments.

A.8.11 Data masking partial match
blocks

Data masking hides sensitive data from unauthorized viewers, blocking exploitation of the exposure for masked data, but it only covers data that is explicitly masked and does not address exposures from error messages, debug logs, or indirect information leaks.

finds

By continuously inspecting data flows and blocking transmissions that contain classified sensitive content, the control stops the unauthorized release of information that would otherwise occur through missing or bypassed access-control checks.

prevents

Source-code protection via configuration-management tools and access-control rules reduces the chance that sensitive implementation details or credentials will be exposed to unauthorized readers.

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.

References