CVE-2026-41983 Null dereference in HarmonyOS
Medium 4.3
Published
Updated
Check this codebase for CVE-2026-41983 and fix it if it is affected.
What it is: CVE-2026-41983 is a medium-severity vulnerability in Huawei HarmonyOS, published on 9 Jun 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-41983 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-41983/ (Markdown: https://insights.sbomify.com/CVE-2026-41983/index.md)
A null pointer dereference in the HarmonyOS browser module allows attackers to cause a denial of service.
- 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-41983?
CVE-2026-41983 is a medium-severity vulnerability in Huawei HarmonyOS, published on 9 Jun 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
Null pointer dereference vulnerability in the browser module. Impact: Successful exploitation of this vulnerability may affect availability.
Weakness: CWE-399
Which versions are affected by CVE-2026-41983?
How do I fix CVE-2026-41983?
No fix has been published for CVE-2026-41983 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-41983 being exploited?
There is no known exploitation of CVE-2026-41983 in the wild and no public exploit code.
Sources
Also known as GHSA-767p-cppf-v3v3.