VulnerabilityPublished 4 Dec 2023Updated 29 May 2025

CVE-2023-40076: Google Android · Information Disclosure

Affects Google AndroidSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.2% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Dec 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Google Android	Affected =14	Fixed in–

AI-suggested

To mitigate CVE-2023-40076, European organizations should: 1) Monitor for and promptly apply official security patches from Google or device manufacturers once available, as no patches are currently linked. 2) Restrict local device access by enforcing strong device authentication methods and limiting the number of users or profiles on Android 14 devices, especially in shared or corporate environments. 3) Implement mobile device management (MDM) solutions that can enforce security policies, restrict installation of untrusted applications, and monitor for suspicious local privilege escalations. 4) Educate users on the risks of installing untrusted applications or granting excessive permissions, as local attackers may exploit this vulnerability via malicious apps. 5) Consider isolating sensitive credential stores or using hardware-backed security features such as Trusted Execution Environments (TEE) or StrongBox where possible to reduce the risk of credential exposure. 6) Conduct regular audits of device configurations and user permissions to detect and remediate potential misuse or unauthorized access. These steps go beyond generic advice by focusing on controlling local access vectors and preparing for patch deployment.

Description

In createPendingIntent of CredentialManagerUi.java, there is a possible way to access credentials from other users due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Impact

For European organizations, this vulnerability poses a risk primarily in environments where Android 14 devices are used and shared among multiple users or where multiple user profiles exist on a single device. The exposure of credentials could lead to unauthorized access to corporate resources, internal applications, or sensitive personal data, undermining confidentiality and potentially facilitating lateral movement within enterprise networks. Organizations with Bring Your Own Device (BYOD) policies or shared device scenarios are particularly at risk. The lack of required user interaction and the ability to exploit the vulnerability with low privileges increase the threat level in environments with less stringent device access controls. While the vulnerability does not directly impact system integrity or availability, the compromise of credentials can lead to broader security incidents, including data breaches or unauthorized access to cloud services and enterprise applications. Given the widespread use of Android devices in Europe for both personal and professional purposes, the vulnerability could have significant implications if exploited in targeted attacks against high-value users or sectors such as finance, government, or critical infrastructure.

CWE-276Incorrect Default Permissions (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
During installation, installed file permissions are set to allow anyone to modify those files.
Architecture and Design · Operation
The architecture needs to access and modification attributes for files to only those users who actually require those actions.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 02:59 UTC

WeaknessesCWE-276

Technical details

References

Community reviews

Related threats