CVE-2026-41964 Race condition in HarmonyOS
High 8.4
Published
Updated
Check this codebase for CVE-2026-41964 and fix it if it is affected.
What it is: CVE-2026-41964 is a high-severity vulnerability in Huawei HarmonyOS, published on 15 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41964 in the wild and no public exploit code.
Affected product: Huawei HarmonyOS. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-41964/ (Markdown: https://insights.sbomify.com/CVE-2026-41964/index.md)
A race condition in HarmonyOS allows attackers to disrupt system availability through permission control flaws.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-41964?
CVE-2026-41964 is a high-severity vulnerability in Huawei HarmonyOS, published on 15 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Permission control vulnerability in the web. Impact: Successful exploitation of this vulnerability may affect availability.
Weakness: CWE-362
Which versions are affected by CVE-2026-41964?
How do I fix CVE-2026-41964?
No fix has been published for CVE-2026-41964 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-41964 being exploited?
There is no known exploitation of CVE-2026-41964 in the wild and no public exploit code.
Sources
Also known as GHSA-9wgr-ww7c-cg24.