CVE-2026-49302 Information disclosure in HarmonyOS
Medium 6.2
Published
Updated
Check this codebase for CVE-2026-49302 and fix it if it is affected.
What it is: CVE-2026-49302 is a medium-severity vulnerability in Huawei HarmonyOS, published on 17 Aug 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-49302 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-49302/ (Markdown: https://insights.sbomify.com/CVE-2026-49302/index.md)
An attacker can exploit a permission control flaw in the notification service to access confidential service data.
- 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-49302?
CVE-2026-49302 is a medium-severity vulnerability in Huawei HarmonyOS, published on 17 Aug 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 notification service module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.
Weakness: CWE-200
Which versions are affected by CVE-2026-49302?
How do I fix CVE-2026-49302?
No fix has been published for CVE-2026-49302 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-49302 being exploited?
There is no known exploitation of CVE-2026-49302 in the wild and no public exploit code.
Sources
Also known as GHSA-3r4g-j3pm-8grm.