Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local foothold via malicious app
-
ExploitInvoke exposed ManagedProvisioning interface
-
ExecutionBypass access control check
-
ImpactSilently install arbitrary applications
Vulnerability Assessment
| Exploitation Conditions | Exploitation requires local presence on the affected Samsung mobile device - typically a malicious or sideloaded application already running - because the vector is AV:L; it is not remotely reachable. Once local, no additional privileges (PR:N) or user interaction (UI:N) are needed to abuse the improper access control in the ManagedProvisioning component to install arbitrary applications. Exploitation is limited to devices running firmware prior to SMR Sep-2026 Release 1; patched builds remove the exposure. The requirement for an attacker-controlled local app substantially reduces realistic risk versus a remote flaw. |
| Impact | Signals are mixed and point to a moderate, locally-scoped risk rather than an urgent priority. The vendor-supplied CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:N) describes a local, low-complexity, zero-privilege, zero-interaction flaw scoring 6.9 (Medium), consistent with 'improper access control in ManagedProvisioning' being abusable by any local actor. There is no CISA KEV listing and no EPSS score in the provided data, and no public exploit is referenced - so there is no evidence of active or imminent widespread exploitation (no public exploit identified at time of analysis). A notable internal conflict exists: the CVSS vector sets VC:H (confidentiality impact) and the Tags say 'Information Disclosure,' yet the description states the flaw 'allows local attackers to install arbitrary applications' - that behavior is an integrity impact (unauthorized software installation), not confidentiality/disclosure. This impact-type mismatch should be verified with Samsung's SMB advisory. The AV:L requirement (attacker needs local presence, typically a malicious or sideloaded app already on the device) meaningfully limits real-world reach, keeping this a defense-in-depth patch rather than an emergency. |
| Exploit ScenarioDerived | A low-privilege malicious application already present on a Samsung device (e.g., sideloaded or from an untrusted store) abuses the improper access control in ManagedProvisioning to silently install additional arbitrary applications without user consent or elevated permissions. Because the CVSS vector is AV:L/PR:N/UI:N, no privileges or user interaction are required once the attacker has local code execution, but local presence on the device is a prerequisite. No public exploit code is referenced in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
Improper access control in Samsung's ManagedProvisioning system component allows a locally present application to install arbitrary packages on affected Galaxy devices running firmware older than the September 2026 Security Maintenance Release (SMR Sep-2026 Release 1). Exploitation requires an attacker-controlled app already executing on the device (AV:L) but demands no additional privileges (PR:N) and no user interaction (UI:N), so a malicious or sideloaded app can drive a privileged provisioning path to install software the user never authorized. No confirmed actively exploited (CISA KEV) status and no publicly available exploit code identified at time of analysis, and the independent reassessment (CVSS 3.1 6.9, C:N/I:H/A:N) frames this as a moderate, locally scoped integrity risk rather than an urgent, remotely reachable one.
RemediationAI
Apply the vendor fix by updating to SMR Sep-2026 Release 1: Vendor-released patch: SMR Sep-2026 Release 1, delivered through Settings > Software update > Download and install (or via Smart Switch/ODIN for managed fleets), then confirm the device's security patch level reads September 2026 or later per the advisory at https://security.samsungmobile.com/securityUpdate.smsb?year=2026&month=09. No standalone vendor workaround was published in the available references, so patching is the only complete remediation. As compensating controls while devices remain unpatched, reduce the precondition the flaw depends on - the presence of an attacker-controlled local app - by disabling 'Install unknown apps' for all sources and keeping Google Play Protect enabled (trade-off: blocks legitimate sideloading and internal enterprise app distribution), and by using Android Enterprise with managed Google Play and a device policy that restricts package installation and locks down provisioning settings (trade-off: requires an EMM/MDM deployment and may restrict user-installed apps). These measures shrink the attack surface but do not patch ManagedProvisioning itself, and they cannot help if a malicious app is already installed, so prioritize firmware updates over compensating controls.
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
ManagedProvisioning (the Android system package com.android.managedprovisioning) is the framework component that handles device setup and enterprise enrollment flows: work profile creation, device-owner and profile-owner provisioning, and managed-device configuration. Because it executes as a privileged system app and brokers package installation and device-policy changes, it holds permissions ordinary applications do not. The flaw is an access-control weakness in that component (no CWE was assigned in the feed; the described behavior maps to the CWE-284/CWE-862 improper-authorization class), meaning an exported entry point or trust boundary inside ManagedProvisioning can be reached or manipulated by another local app without adequate permission or caller validation, letting the caller piggyback on the component's elevated privileges to install arbitrary applications. Both the vendor's CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N, 6.9) and the independent CVSS 3.1 reassessment (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) agree on local access, low complexity, no privileges and no user interaction; they diverge on which property is impacted, with the 4.0 vector and the source tags ('Information Disclosure') pointing at confidentiality while the independent assessment points at integrity, which is also what the description (arbitrary app installation) implies. This divergence most likely reflects metric-mapping differences between CVSS versions and should not be read as a higher combined impact. The affected CPE (cpe:2.3:a:samsung_mobile:samsung_mobile_devices:*:*:*:*:*:*:*:*) is version-wildcarded, so the vulnerability record does not enumerate individual models or builds; the Samsung SMR advisory is the authoritative list of affected devices and the build string that resolves the issue.
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:H/VI:N/VA:N/SC:N/SI:N/SA:N
Local access needed (AV:L) via an on-device app with no privileges or interaction (PR:N/UI:N); installing arbitrary apps is an integrity impact (I:H), not confidentiality or availability.
Primary rating from Vendor (SamsungMobile).
CVSS VectorVendor: SamsungMobile
DescriptionCVE.org
Improper access control in ManagedProvisioning prior to SMR Sep-2026 Release 1 allows local attackers to install arbitrary applications.
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-91157
GHSA-crm9-6p8f-6cx9
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB