cve.bz

CVE-2025-66320 huawei harmonyos: Race Condition

4.7 mediumEPSS 0.07%

Medium (4.7) in huawei harmonyos. EPSS 0.07% estimated probability of exploitation activity in the next 30 days.

On this page
Multi-thread race condition vulnerability in the camera framework module. Impact: Successful exploitation of this vulnerability may affect availability.

Severity

CVSS 3.1

4.7 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.07% (unchanged from 0.07% a week ago; 0.07% 30 days ago) estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-12-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-66320 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-66320?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-66320?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-66320 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-66320

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-66320](https://cve.bz/cve/badge/CVE-2025-66320.svg)](https://cve.bz/cve/CVE-2025-66320)

HTML:

<a href="https://cve.bz/cve/CVE-2025-66320"><img src="https://cve.bz/cve/badge/CVE-2025-66320.svg" alt="CVE-2025-66320"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
huawei:harmonyos5.0.1
huawei:harmonyos5.1.0
huawei:harmonyos6.0.0

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON