# CVE-2026-56980: Android Framework out-of-bounds write in data flow manager

Source: https://junglewise.ai/threats/cve-2026-56980-in-createdataflowasync-of-data-flow-manager-cc-there-is-a  
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-56980 · Severity: info · Published 2026-11-10

The Android Framework contains a memory vulnerability in its data flow management component that could allow a local attacker to write outside allocated memory boundaries due to integer overflow. An attacker with local access could exploit this to gain elevated system privileges without requiring additional permissions or user interaction.

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

## Quick answers

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

**How severe is CVE-2026-56980?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Google Android Before security patch level 2026-11-05.

**Is there a fix for CVE-2026-56980?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

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

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

An integer overflow in the createDataFlowAsync function of data_flow_manager.cc allows an attacker to trigger an out-of-bounds write in shared memory. The vulnerability requires local access but no additional execution privileges, and exploitation does not require user interaction. This leads to local privilege escalation.

## Affected products

- Google Android Before security patch level 2026-11-05

## Timeline

- 2026-11-10: disclosed

## 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)