CVE-2026-41960 Information disclosure in EMUI
Medium 5.8
Published
Updated
Check this codebase for CVE-2026-41960 and fix it if it is affected.
What it is: CVE-2026-41960 is a medium-severity vulnerability in Huawei EMUI, published on 15 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-41960 in the wild and no public exploit code.
Affected product: Huawei EMUI. 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-41960/ (Markdown: https://insights.sbomify.com/CVE-2026-41960/index.md)
An attacker can exploit a permission control flaw in Huawei EMUI and HarmonyOS calls to disclose sensitive information, affecting availability.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-41960?
CVE-2026-41960 is a medium-severity vulnerability in Huawei EMUI, published on 15 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Permission control vulnerability in calls. Impact: Successful exploitation of this vulnerability may affect availability.
Weakness: CWE-200
Which versions are affected by CVE-2026-41960?
How do I fix CVE-2026-41960?
No fix has been published for CVE-2026-41960 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-41960 being exploited?
There is no known exploitation of CVE-2026-41960 in the wild and no public exploit code.
Sources
Also known as GHSA-xp9m-hqhq-462q.