CVE-2026-56947 · Runtime
NO FIX YET
A flaw in Android's PhoneInterfaceManager getCarrierRestrictionStatus function lets an app bypass a permission check through a confused deputy. An attacker-controlled app on the device can read information it should not be able to see.
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.
The sources describe a local information disclosure in Android's telephony code, with no extra privileges or user interaction needed. Which Android versions and devices are affected is unknown from the sources.
Who cares android, mobile
Unknown from the sources.
No fix yet, per the sources.
In getCarrierRestrictionStatus of PhoneInterfaceManager.java, there is a possible permission bypass due to a confused deputy. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
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.