Liteos-A has an insecure storage of sensitive information vulnerability

published 2025-03-04 last yr. modified 2026-06-17 4mo ago also EUVD-2025-7584

cvss: 5.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits: 0; none known

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause information leak through out-of-bounds read bypass permission check.

Is CVE-2025-21098 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: last yr. (2025-03-04)

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected products

OpenHarmony OpenHarmony

Classification

Weakness

CWE-922 Insecure Storage of Sensitive Information
CWE-125 Out-of-bounds Read

References

gitee.com /openharmony/security/blob/master/zh/security-disclosure/2025/2025-03.md
vendor-advisory

Sources

CVE List CVE-2025-21098
NVD CVE-2025-21098

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.