CVE-2025-27247VulnerabilityPublished 8 Jun 2025Updated 9 Jun 2025

CVE-2025-27247: OpenHarmony · Improper Preservation of Permissions

Affects OpenHarmonySource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
OpenHarmony OpenHarmony	Affected =5.0.1	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should first identify all devices running OpenHarmony, particularly version 5.0.3 and earlier, including 5.0.1. In the interim, organizations should enforce strict physical and logical access controls to limit local access to devices, including the use of secure boot, device hardening, and network segmentation to isolate vulnerable devices. Implementing robust monitoring and logging can help detect unauthorized access attempts. Additionally, organizations should review and tighten permission configurations on affected devices to minimize the risk of unauthorized data access. Where possible, replacing or upgrading devices to versions confirmed to be free of this vulnerability is advisable. Finally, educating staff about the risks of local attacks and insider threats can reduce the likelihood of exploitation.

Description

in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.

Impact

For European organizations, the impact of CVE-2025-27247 depends largely on the adoption of OpenHarmony-based devices within their infrastructure or supply chains. Given OpenHarmony's focus on IoT and smart devices, sectors such as manufacturing, smart city infrastructure, healthcare, and telecommunications could be affected if they deploy devices running vulnerable versions. The information leak could expose sensitive operational data, user information, or device configurations, potentially leading to privacy violations or aiding further attacks. Although the vulnerability requires local access, in environments where physical security is less stringent or where insider threats exist, this could be a significant risk. Additionally, compromised IoT devices could serve as footholds for lateral movement within networks. The medium severity rating suggests that while the vulnerability is not critical, it still poses a meaningful risk, especially in high-security environments or where sensitive data is processed. European organizations must consider the regulatory implications of data leaks under GDPR, which could lead to compliance issues and fines if personal data is exposed.

CWE-281Improper Preservation of Permissions (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

gitee.com/openharmony/security/blob/master/zh/security-disclosure/2025/2025-06.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2025, 00:40 UTC

WeaknessesCWE-281

Technical details

References

Community reviews

Related threats