CVE-2026-21012: Medium severity Samsung AODManager vulnerability
Published Apr 13, 2026
·Updated
External control of file name in AODManager prior to SMR Apr-2026 Release 1 allows privileged local attacker to create file with system privilege.
Affected Software
80 affected components
Samsung AODManager<SMR Apr-2026 Release 1
Samsung Android=14.0
Samsung Android=14.0-smr-apr-2022-r1
Samsung Android=14.0-smr-apr-2023-r1
Samsung Android=14.0-smr-apr-2024-r1
Samsung Android=14.0-smr-apr-2025-r1
Samsung Android=14.0-smr-aug-2022-r1
Samsung Android=14.0-smr-aug-2023-r1
Samsung Android=14.0-smr-aug-2024-r1
Samsung Android=14.0-smr-aug-2025-r1
Samsung Android=14.0-smr-dec-2021-r1
Samsung Android=14.0-smr-dec-2022-r1
Samsung Android=14.0-smr-dec-2023-r1
Samsung Android=14.0-smr-dec-2024-r1
Samsung Android=14.0-smr-dec-2025-r1
Samsung Android=14.0-smr-feb-2022-r1
Samsung Android=14.0-smr-feb-2023-r1
Samsung Android=14.0-smr-feb-2024-r1
Samsung Android=14.0-smr-feb-2025-r1
Samsung Android=14.0-smr-feb-2026-r1
Samsung Android=14.0-smr-jan-2022-r1
Samsung Android=14.0-smr-jan-2023-r1
Samsung Android=14.0-smr-jan-2024-r1
Samsung Android=14.0-smr-jan-2025-r1
Samsung Android=14.0-smr-jan-2026-r1
Samsung Android=14.0-smr-jul-2022-r1
Samsung Android=14.0-smr-jul-2023-r1
Samsung Android=14.0-smr-jul-2024-r1
Samsung Android=14.0-smr-jul-2025-r1
Samsung Android=14.0-smr-jun-2022-r1
Samsung Android=14.0-smr-jun-2023-r1
Samsung Android=14.0-smr-jun-2024-r1
Samsung Android=14.0-smr-jun-2025-r1
Samsung Android=14.0-smr-mar-2022-r1
Samsung Android=14.0-smr-mar-2023-r1
Samsung Android=14.0-smr-mar-2024-r1
Samsung Android=14.0-smr-mar-2025-r1
Samsung Android=14.0-smr-mar-2026-r1
Samsung Android=14.0-smr-may-2022-r1
Samsung Android=14.0-smr-may-2023-r1
Samsung Android=14.0-smr-may-2024-r1
Samsung Android=14.0-smr-may-2025-r1
Samsung Android=14.0-smr-nov-2021-r1
Samsung Android=14.0-smr-nov-2022-r1
Samsung Android=14.0-smr-nov-2023-r1
Samsung Android=14.0-smr-nov-2024-r1
Samsung Android=14.0-smr-nov-2025-r1
Samsung Android=14.0-smr-oct-2022-r1
Samsung Android=14.0-smr-oct-2023-r1
Samsung Android=14.0-smr-oct-2024-r1
Samsung Android=14.0-smr-oct-2025-r1
Samsung Android=14.0-smr-sep-2022-r1
Samsung Android=14.0-smr-sep-2023-r1
Samsung Android=14.0-smr-sep-2024-r1
Samsung Android=14.0-smr-sep-2025-r1
Samsung Android=15.0
Samsung Android=15.0-smr-apr-2025-r1
Samsung Android=15.0-smr-aug-2025-r1
Samsung Android=15.0-smr-dec-2025-r1
Samsung Android=15.0-smr-feb-2025-r1
Samsung Android=15.0-smr-feb-2026-r1
Samsung Android=15.0-smr-jan-2025-r1
Samsung Android=15.0-smr-jan-2026-r1
Samsung Android=15.0-smr-jul-2025-r1
Samsung Android=15.0-smr-jun-2025-r1
Samsung Android=15.0-smr-mar-2025-r1
Samsung Android=15.0-smr-mar-2026-r1
Samsung Android=15.0-smr-may-2025-r1
Samsung Android=15.0-smr-nov-2025-r1
Samsung Android=15.0-smr-oct-2025-r1
Samsung Android=15.0-smr-sep-2025-r1
Samsung Android=16.0
Samsung Android=16.0-smr-aug-2025-r1
Samsung Android=16.0-smr-dec-2025-r1
Samsung Android=16.0-smr-feb-2026-r1
Samsung Android=16.0-smr-jan-2026-r1
Samsung Android=16.0-smr-mar-2026-r1
Samsung Android=16.0-smr-nov-2025-r1
Samsung Android=16.0-smr-oct-2025-r1
Samsung Android=16.0-smr-sep-2025-r1
Event History
Apr 13, 2026
CVE Published
via MITRE·05:04 AM
Data Sourced
via MITRE·05:04 AM
DescriptionWeakness
Data Sourced
via NVD·06:16 AM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-21012?
The CVE-2026-21012 vulnerability has a critical severity rating due to its potential to allow privileged local attackers to execute malicious actions.
2
How do I fix CVE-2026-21012?
To fix CVE-2026-21012, users should update their Samsung AODManager software to the SMR Apr-2026 Release 1 or later.
3
What systems are affected by CVE-2026-21012?
CVE-2026-21012 affects Samsung AODManager prior to the SMR Apr-2026 Release 1 and specific versions of Samsung Android.
4
What kind of attacks can CVE-2026-21012 facilitate?
CVE-2026-21012 can be exploited by privileged local attackers to create files with system-level privileges.
5
Is there a workaround for CVE-2026-21012?
There are no known workarounds for CVE-2026-21012 other than applying the proper software updates.