Quick answers
- Is CVE-2026-21120 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-21120 being exploited in the wild.
- How severe is CVE-2026-21120?
- Informational severity, published 12 October 2026.
- Which products and versions are affected?
- Samsung Android firmware prior to SMR Oct-2026 Release 1.
- Is there a fix for CVE-2026-21120?
- Yes: fixed in SMR Oct-2026 Release 1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-21120 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-21120?
- Check whether you run Samsung Android firmware at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: SMR Oct-2026 Release 1
Technical details
A use-after-free vulnerability exists in the WSM service prior to the SMR (Samsung Mobile Release) October 2026 Release 1. The vulnerability requires local access to the device and allows privilege escalation to system level. This memory safety bug permits arbitrary code execution once memory is freed and reallocated.
Affected products
- Samsung Android firmware prior to SMR Oct-2026 Release 1
Timeline
- 2026-10-12: disclosed