Quick answers
- Is CVE-2026-56947 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56947 being exploited in the wild.
- How severe is CVE-2026-56947?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Android versions prior to 2026-11-05 security patch level.
- Is there a fix for CVE-2026-56947?
- A patch was published on 2026-11-05. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56947 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-56947?
- Check whether you run Google Android at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A confused deputy vulnerability exists in the getCarrierRestrictionStatus method of PhoneInterfaceManager.java, allowing a local attacker to bypass permission checks. The vulnerability requires local code execution but no additional privileges and affects the Telephony framework component. An attacker gains unauthorized read access to carrier restriction status that should be protected by platform permissions.
Affected products
- Google Android versions prior to 2026-11-05 security patch level
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched