# CVE-2026-59597: Android Framework privilege escalation in telephony tunnel management

Source: https://junglewise.ai/threats/cve-2026-59597-in-binddataservice-of-dataservicemanager-java-there-is-a-possible  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-59597 · Severity: info · Published 2026-11-10

An Android system component that manages privileged telephony tunnel permissions contains a logic error that allows a local attacker to retain elevated permissions after a configuration update. This could enable an attacker to gain unauthorized access to sensitive telephony functions without needing to exploit additional vulnerabilities or interact with users.

Technologies: [Google Android](https://junglewise.ai/threats/technologies/android). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-59597 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-59597 being exploited in the wild.

**How severe is CVE-2026-59597?** 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-59597?** Yes: fixed in Android security patch level 2026-11-05 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-59597 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-59597?** 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.

## How to fix

- Fixed in Android security patch level 2026-11-05 or later

## Technical details

A logic error in the DataServiceManager.java bindDataService method in the Android Framework's Telephony component fails to properly revoke privileged tunnel management permissions during configuration updates, allowing an unprivileged local process to retain escalated capabilities. The vulnerability requires local code execution but no additional user interaction or elevated privileges to exploit. A fix has been released in the 2026-11-05 Android security patch level.

## Affected products

- Google Android versions prior to 2026-11-05 security patch level

## Timeline

- 2026-11-10: disclosed
- 2026-11-05: patched

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01)

## Related threats

- [Google Android Bluetooth buffer overflow in acquireMemory](https://junglewise.ai/threats/cve-2026-95405-in-acquirememory-of-bt-bqr-offload-cc-there-is-a-possible-way-to)
- [ST NFC HAL out-of-bounds write in global memory](https://junglewise.ai/threats/cve-2026-95400-in-stnfc-hal-write-of-hal-st21nfc-cc-there-is-a-possible-way-to)
- [Android HEVC decoder buffer overflow in sub_layer_hrd_parameters](https://junglewise.ai/threats/cve-2026-95397-in-sub-layer-hrd-parameters-of-hevc-decoder-there-is-a-possible)
- [Android framework memory exhaustion in message queue handling](https://junglewise.ai/threats/cve-2026-59632-in-respondreceivedmessage-of-mtsmessagecontroller-cpp-there-is-a)
- [Android use-after-free in UssiController connection listener](https://junglewise.ai/threats/cve-2026-59626-in-sendinfo-of-ussicontroller-cpp-there-is-a-possible-way-to)