HarmonyOS: Improper Authentication
CVE-2025-53169 is a high-severity improper authentication vulnerability in HarmonyOS from Huawei, with a CVSS 3.1 base score of 7.6 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected HarmonyOS versions: 5.1.0; 5.0.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.15% 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 HarmonyOS you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on consumer.huawei.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
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- 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
- LowLimited modification of data is possible.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L. Scored by CNA (huawei.com).
Official description
Vulnerability of bypassing the process to start SA and use related functions on distributed cameras Impact: Successful exploitation of this vulnerability may allow the peer device to use the camera without user awareness.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in HarmonyOS
- 7.1 High severity
- 8.6 High severity
Recent Improper Authentication vulnerabilities
- 7.3 High severity
- 8.8 High severity
- 8.8 High severity
- 9.6 Critical severity
- 8.8 High severity
- 10.0 Critical severity
Spotted an error? Tell us.