Local privileged API access via missing authorization
Published Jan 9, 2026 · Updated Jan 9, 2026
Improper access control in Samsung Mobile Devices before SMR Jan-2026 Release 1 allows local users to invoke privileged SLocation APIs. SLocation exposes privileged operations without the access-control check required to reject unauthorized local callers; Samsung has not disclosed the specific API entry points. A low-privileged local context on Android 15 or 16 is required, and the published impact is access to SLocation capabilities rather than arbitrary code execution.
Summary
What happened
Improper access control in Samsung Mobile Devices before SMR Jan-2026 Release 1 allows local users to invoke privileged SLocation APIs. SLocation exposes privileged operations without the access-control check required to reject unauthorized local callers; Samsung has not disclosed the specific API entry points. A low-privileged local context on Android 15 or 16 is required, and the published impact is access to SLocation capabilities rather than arbitrary code execution.
The record
- CVE
- CVE-2026-20970
- Published
- Jan 9, 2026
- Updated
- Jan 9, 2026
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-284, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 9, 2026CVE publishedPublication date reported by the CVE source.
- Jan 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo