Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall malicious app on device
-
DeliveryInvoke exported CreditCardRegisterActivity
-
ExploitSupply crafted input bypassing validation
-
ExecutionLaunch arbitrary activity as Samsung Checkout
-
ImpactGain Checkout-privileged component access
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Requires local code execution on the device via a malicious or compromised app that can invoke Samsung Checkout's CreditCardRegisterActivity component; the specific prerequisite is that this activity performs improper input validation allowing it to be driven to launch an arbitrary activity with Samsung Checkout privileges. Exploitation is limited to Samsung Checkout versions prior to 5.1.03.1 and to the local device context - there is no remote vector (AV:L), so an attacker must first get code running on the device, though no additional authentication or user interaction is needed (PR:N/UI:N). |
| Impact | This is a medium-severity, locally-exploitable flaw whose signals are internally consistent and point to limited real-world urgency. The only CVSS vector provided is a CVSS 4.0 base vector (AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N, scoring 5.1), which indicates local attack vector, low complexity, no privileges and no user interaction required, with only low confidentiality and low integrity impact and no availability impact. The local attack vector (AV:L) is the dominant mitigating factor: exploitation requires an attacker to already be executing code on the device (e.g., a malicious app), not a remote network attacker. There is no KEV listing, no EPSS score, and no POC provided in the input, so exploitation status is 'no public exploit identified at time of analysis.' No SSVC data is provided. Note a signal to verify: the input Tags label this 'Information Disclosure,' but the description describes launching an arbitrary activity with Samsung Checkout's privileges - a component-permission/confused-deputy issue - which only partially aligns with pure information disclosure; the VC:L/VI:L impacts are modest and consistent with limited exposure rather than full compromise. Overall this is a genuine but low-priority local privilege/component-access issue, not a high-urgency remote threat. |
| Exploit ScenarioDerived | A malicious or compromised application already installed on a Samsung device invokes the improperly-validated CreditCardRegisterActivity in Samsung Checkout, passing crafted input that causes it to launch an arbitrary activity under Samsung Checkout's privileges. Because the flaw is local and low-complexity (AV:L/AC:L) and needs no special privileges or user interaction (PR:N/UI:N), any sideloaded or trojanized app could attempt it. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Local attackers who can run code on a Samsung device can exploit improper input validation in Samsung Checkout's CreditCardRegisterActivity to launch arbitrary activities using Samsung Checkout's own privileges, yielding low-level confidentiality and integrity exposure. The flaw affects Samsung Checkout versions prior to 5.1.03.1 and requires local code execution on the device, but no additional authentication or user interaction (CVSS:4.0 AV:L/AC:L/PR:N/UI:N, score 5.1; independently assessed as CVSS:3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N). No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV; overall this is a medium-severity, locally-scoped issue with limited real-world urgency.
RemediationAI
Apply the vendor fix by upgrading Samsung Checkout to version 5.1.03.1 or later; this is the exact fixed version named in the advisory (https://security.samsungmobile.com/serviceWeb.smsb?year=2026&month=10), and device users should update through the Galaxy Store or the Samsung system update mechanism as soon as it is offered. Until the update is applied, the most effective compensating control is to reduce the local attack surface by avoiding installation of untrusted or sideloaded applications and by keeping Google Play Protect and Samsung's app-scanning features enabled - the trade-off is reduced flexibility for users who routinely sideload APKs, and this does not eliminate exploitation by an already-installed malicious app. Developers integrating Samsung Checkout should validate and sanitize all Intent extras and caller identity in CreditCardRegisterActivity and, where the checkout flow permits, require a signature-level permission or restrict the activity to internal callers; the trade-off is that tightening the component's export or permission model can break legitimate merchant/partner integrations that rely on the current entry point, so it should be tested against supported payment flows. Because the issue is local-only (AV:L) and requires an attacker to already have code executing on the device, network-level defenses (WAF, firewall, IDS rules) are not applicable controls. No vendor-released patch identifier beyond the 5.1.03.1 version number is available, and no additional mitigation is offered in the reference advisory.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability sits in an Android application component: the CreditCardRegisterActivity exported (or otherwise reachable) inside Samsung Checkout, the payment SDK/app preloaded on many Samsung Galaxy devices. Because the activity does not properly validate incoming input - intent data, extras, or the originating caller - a locally installed or compromised application can drive it into launching an arbitrary activity that then executes with Samsung Checkout's UID and privileges. This is the classic Android component-exposure pattern: root cause class is improper input validation (CWE-20) with overtones of improper export of an Android application component (CWE-926), where a privileged app trusts an Intent it should have validated, sanitized, or gated behind a signature-level permission. The CVSS:4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N) confirms the attack is local, low complexity, unauthenticated, and requires no user interaction, with only low confidentiality and integrity impact and no availability impact; the independently assessed CVSS:3.1 vector agrees (AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N). No CWE was supplied by the reporter, and no CPE strings were provided, so exact package/build identifiers beyond the version range are not confirmed from the available data.
Know when Android gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Local co-resident app can invoke the component with no privileges or interaction, giving AV:L/AC:L/PR:N/UI:N; only limited confidentiality and integrity impact, hence C:L/I:L/A:N.
Primary rating from Vendor (samsung).
CVSS VectorVendor: samsung
DescriptionCVE.org
Improper input validation in CreditCardRegisterActivity of Samsung Checkout prior to version 5.1.03.1 allows local attackers to launch arbitrary activity with Samsung Checkout privileges.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
EUVD-2026-97192
GHSA-vv79-rj27-885f
NVD
CVE.org
EPSS
Exploit-DB