Data exposure via improper permission enforcement
Published Nov 28, 2025 · Updated Nov 28, 2025
Permission control failure in Huawei HarmonyOS 5.0.1, 5.1.0, and 6.0.0 allows physically proximate attackers to expose service data. The file management module improperly enforces permissions, but Huawei has not disclosed the affected operation, data path, or input that triggers the check failure. Exploitation requires physical access and user interaction, and the documented consequence is unauthorized data exposure with no availability impact.
Summary
What happened
Permission control failure in Huawei HarmonyOS 5.0.1, 5.1.0, and 6.0.0 allows physically proximate attackers to expose service data. The file management module improperly enforces permissions, but Huawei has not disclosed the affected operation, data path, or input that triggers the check failure. Exploitation requires physical access and user interaction, and the documented consequence is unauthorized data exposure with no availability impact.
The record
- CVE
- CVE-2025-64312
- Published
- Nov 28, 2025
- Updated
- Nov 28, 2025
- Vendor
- MindSpore
- Product
- HarmonyOS
- Classifications
- CWE-200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 28, 2025CVE publishedPublication date reported by the CVE source.
- Nov 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.0.1
- Affected versionversion=5.1.0
- Affected versionversion=6.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo