Quick answers
- Is CVE-2026-21128 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-21128 being exploited in the wild.
- How severe is CVE-2026-21128?
- Informational severity, published 12 October 2026.
- Which products and versions are affected?
- Samsung Checkout prior to 5.1.03.1.
- Is there a fix for CVE-2026-21128?
- Yes: fixed in 5.1.03.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-21128 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-21128?
- Check whether you run Samsung Checkout 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: 5.1.03.1
Technical details
The CreditCardRegisterActivity component in Samsung Checkout fails to properly validate user-supplied input prior to version 5.1.03.1, enabling a local attacker to trigger unintended activity execution with the application's system privileges. This requires local access to the device but does not require user interaction. A successful exploit could allow arbitrary code execution or data theft within the payment application's context.
Affected products
- Samsung Checkout prior to 5.1.03.1
Timeline
- 2026-10-12: disclosed