CVE-2026-21050 Information disclosure in Samsung Mobile Devices
Medium 5.1
Published
Updated
Check this codebase for CVE-2026-21050 and fix it if it is affected.
What it is: CVE-2026-21050 is a medium-severity vulnerability in Samsung Mobile Devices, published on 10 Jul 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-21050 in the wild and no public exploit code.
Affected product: Samsung Mobile Devices. 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-21050/ (Markdown: https://insights.sbomify.com/CVE-2026-21050/index.md)
Local attackers can access sensitive information due to improper access control in SmartThingsKit on Samsung mobile devices.
- 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-21050?
CVE-2026-21050 is a medium-severity vulnerability in Samsung Mobile Devices, published on 10 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Improper access control in SmartThingsKit prior to SMR Jul-2026 Release 1 allows local attackers to access sensitive information.
Which versions are affected by CVE-2026-21050?
How do I fix CVE-2026-21050?
No fix has been published for CVE-2026-21050 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-21050 being exploited?
There is no known exploitation of CVE-2026-21050 in the wild and no public exploit code.
Sources
Also known as GHSA-vp97-c768-8wqr.