What is the CVSS score of CVE-2025-21098?

CVE-2025-21098 has a CVSS 3.1 base score of 5.5 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of Openharmony are affected by CVE-2025-21098?

Organizations using OpenHarmony should be aware of moderate risk from CVE-2025-21098 rated CVSS 5.5. Exploitation could compromise the security of affected deployments.

How to fix or mitigate CVE-2025-21098?

Within 30 days: Identify affected systems running OpenHarmony and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Openharmony CVE-2025-21098

MEDIUM

Insecure Storage of Sensitive Information (CWE-922)

2025-03-04 scy@openharmony.io

Buffer Overflow Openharmony

5.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:29 vuln.today

CVE Published

Mar 04, 2025 - 04:15 nvd

MEDIUM 5.5

DescriptionCVE.org

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

AnalysisAI

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause information leak through out-of-bounds read bypass permission check. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-922. in OpenHarmony v5.0.2 and prior versions allow a local attacker cause information leak through out-of-bounds read bypass permission check. Affected products include: Openatom Openharmony.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.