CVE-2026-125715 · Infrastructure
NO FIX YET
Samsung mTower, the TEE component on Samsung devices, does not check access for trusted application (TA) sessions. A normal-world app can open sessions, invoke their commands, or close existing sessions when it knows their identifiers, and the impact depends on the affected TA.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Affects Samsung devices running the mTower trusted execution environment; the sources do not list affected models or firmware versions. The impact depends on which trusted applications are installed. unknown
Who cares android, mtower, samsung, trusted-execution
Unknown from the sources.
No fix yet, per the sources.
Samsung mTower lacks access control for TA sessions, allowing a Normal World application to open TA sessions and invoke their commands, or use a close existing sessions if thier identifiers are known, The impact depends on the affected TA.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.