# CVE-2026-58865: Android Framework denial of service in PduParser

Source: https://junglewise.ai/threats/cve-2026-58865-in-multiple-functions-of-pduparser-java-there-is-a-possible  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-05. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-58865 · Severity: high · CVSS 7.5 · Published 2026-10-05

A flaw in Android's PDU message parser can crash the device or cause persistent service interruption with a specially crafted message, requiring no special permissions and no user interaction. An attacker can send a malicious message to any Android device to trigger a remote denial of service.

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

## Quick answers

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

**How severe is CVE-2026-58865?** High severity, with a CVSS score of 7.5, published 5 October 2026.

**Which products and versions are affected?** Google Android 14, 15, 16, 16-qpr2, 17 (all vulnerable; fixed in these versions).

**Is there a fix for CVE-2026-58865?** Yes: fixed in Android 14, 15, 16, 16-qpr2, 17 (security update October 1, 2026). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-58865 attacked?** It is attacked over the network, in an operating system.

**Am I affected by CVE-2026-58865?** 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 14, 15, 16, 16-qpr2, 17 (security update October 1, 2026)

## Technical details

The vulnerability exists in multiple functions of PduParser.java due to missing bounds checks that allow an attacker to trigger denial of service. The flaw is reachable over the network without requiring additional execution privileges or user interaction. A remote attacker can exploit this to cause application crashes or system instability on affected Android devices.

## Affected products

- Google Android 14, 15, 16, 16-qpr2, 17 (all vulnerable; fixed in these versions)

## Timeline

- 2026-10-05: disclosed: Published in Android Security & Privacy Year in Review October 2026 bulletin

## References

- [https://source.android.com/docs/security/bulletin/2026/2026-10-01](https://source.android.com/docs/security/bulletin/2026/2026-10-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)