CVE-2026-58554
Summary
| CVE | CVE-2026-58554 |
|---|---|
| State | PUBLISHED |
| Assigner | huawei |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-15 13:17:29 UTC |
| Updated | 2026-07-15 16:24:31 UTC |
| Description | Permission control vulnerability in the Settings module. Impact: Successful exploitation of this vulnerability may affect service confidentiality. |
Risk And Classification
Primary CVSS: v3.1 6.6 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L
EPSS: 0.000770000 probability, percentile 0.001560000 (date 2026-07-19)
Problem Types: CWE-200 | CWE-200 CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 6.6 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L |
| 3.1 | CNA | CVSS | 6.6 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
NoneUser Interaction
RequiredScope
UnchangedConfidentiality
HighIntegrity
LowAvailability
LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Huawei | HarmonyOS | affected 4.3.1 | Not specified |
| CNA | Huawei | HarmonyOS | affected 4.3.0 | Not specified |
| CNA | Huawei | HarmonyOS | affected 4.2.0 | Not specified |
| CNA | Huawei | HarmonyOS | affected 4.0.0 | Not specified |
| CNA | Huawei | EMUI | affected 15.0.0 | Not specified |
| CNA | Huawei | EMUI | affected 14.2.0 | Not specified |
| CNA | Huawei | EMUI | affected 14.0.0 | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| consumer.huawei.com/en/support/bulletin/2026/7 | [email protected] | consumer.huawei.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.