# CVE-2026-56898: Android AES-256-CMAC message authentication code forgery

Source: https://junglewise.ai/threats/cve-2026-56898-in-aes256-cmac-sw-of-aes-rs-there-is-a-possible-way-to-forge  
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-56898 · Severity: info · Published 2026-11-10

Android devices use AES-256-CMAC in security-critical code to authenticate messages. A flaw in the implementation allows an attacker to forge valid message authentication codes for modified messages, potentially allowing privilege escalation or tampering with protected data without detection.

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

## Quick answers

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

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

**Which products and versions are affected?** Google Android.

**Is there a fix for CVE-2026-56898?** 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-56898 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-56898?** Check whether you run Google Android. 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

The aes256_cmac_sw function in aes.rs implements AES-256-CMAC incorrectly, allowing message authentication code forgery on multi-block messages due to improper cryptographic usage. An attacker with local access can exploit this to forge authentication codes without requiring elevated privileges, leading to local privilege escalation.

## Affected products

- Google Android

## Timeline

- 2026-11-10: disclosed
- 2026-11-10: advisory

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