Android: Use of Uninitialized Variable
CVE-2026-55280 is a high-severity use of uninitialized variable vulnerability in Android 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 attacker with a low-privileged account, without any action from a user. Affected Android versions: 17; 16-qpr2; 16. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.23% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Android you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on source.android.com for workarounds and exact fixed builds.
Affected products and versions
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
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- 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:L/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
In multiple locations, there is a possible out-of-bounds write due to uninitialized data. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Uninitialized Variable
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
How developers prevent this class of flaw
- Ensure that critical variables are initialized before first use.
- Most compilers will complain about the use of uninitialized variables if warnings are turned on.
- When using a language that does not require explicit declaration of variables, run or compile the software in a mode that reports undeclared or unknown variables. This may indicate the presence of a typographic error in the variable's name.
More Use of Uninitialized Variable vulnerabilities (CWE-457)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Android
- 8.4 High severity
- 8.4 High severity
- 7.8 High severity
- 7.8 High severity
- 8.4 High severity
- 7.8 High severity
Recent Use of Uninitialized Variable vulnerabilities
- 8.7 High severity
- 8.1 High severity
- 8.1 High severity
- 8.8 High severity
- 9.1 Critical severity
- 9.6 Critical severity
Spotted an error? Tell us.