Quick answers
- Is CVE-2025-21043 exploited in the wild?
- Yes. CVE-2025-21043 is known to be exploited in the wild, first recorded on 2 October 2025. Treat it as urgent.
- How severe is CVE-2025-21043?
- Critical severity, with a CVSS score of 9.8, published 2 October 2025.
- Which products and versions are affected?
- Samsung Android Prior to SMR Sep-2025 Release 1.
- Is there a fix for CVE-2025-21043?
- A patch was published on 2025-09-12: Addressed in SMR Sep-2025 Release 1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-21043 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2025-21043?
- Check whether you run Samsung Mobile Devices. 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.
Technical details
An out-of-bounds write vulnerability (CWE-787) exists in the libimagecodec.quram.so library on Samsung mobile devices. The flaw is triggered during the processing of malformed image files, allowing a remote attacker to overwrite memory and achieve arbitrary code execution. While some assessments suggest user interaction (UI:R) may be required to trigger the image processing, NIST has rated this as a network-based attack with no privileges required. The vulnerability was addressed in the Samsung SMR September 2025 security update. CISA has confirmed active exploitation of this flaw.
Affected products
- Samsung Android Prior to SMR Sep-2025 Release 1
Timeline
- 2025-09-12: disclosed: Initial disclosure by Samsung Mobile
- 2025-09-12: patched: Addressed in SMR Sep-2025 Release 1
- 2025-10-02: kev added: Added to CISA Known Exploited Vulnerabilities catalog