Quick answers
- Is CVE-2026-21119 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-21119 being exploited in the wild.
- How severe is CVE-2026-21119?
- Informational severity, published 12 October 2026.
- Which products and versions are affected?
- Samsung Android firmware versions prior to SMR Oct-2026 Release 1.
- Is there a fix for CVE-2026-21119?
- 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-21119 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-21119?
- 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
An out-of-bounds read and write vulnerability exists in lib_sag_ai_sound_sep_v2.00.so, a Samsung audio separation library. Local attackers can exploit this to access memory outside the intended buffer boundaries. The vulnerability was fixed in the October 2026 Security Maintenance Release 1.
Affected products
- Samsung Android firmware versions prior to SMR Oct-2026 Release 1
Timeline
- 2026-10-12: disclosed