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