High Threat Security Alert (A26-03-02): Multiple Vulnerabilities in Android


 

Published on: 03 March 2026

Description:

Google has released Android Security Bulletin March 2026 to fix multiple security vulnerabilities in Android operating system. The list of security updates can be found at:
https://source.android.com/docs/security/bulletin/2026/2026-03-01

Android indicates that a memory corruption vulnerability (CVE-2026-21385) may be under limited, targeted exploitation. System administrators are advised to take immediate actions to patch your affected systems to mitigate the elevated risk of cyber attacks.

 

Affected Systems:

  • Android version 14, 15, 16 and 16-qpr2

 

Impact:

Successful exploitation of the vulnerabilities could lead to remote code execution, denial of service, elevation of privilege or information disclosure on an affected system.

 

Recommendation:

Some manufacturers have fixed or have planned to fix the vulnerabilities in their Android systems. Users are recommended to consult the product vendors to confirm the availability of patches. If patches are available, users should upgrade to the fixed versions or follow the recommendations provided by the product vendors to mitigate the risk.

 

More Information:

  • https://source.android.com/docs/security/bulletin/2026/2026-03-01
  • https://www.hkcert.org/security-bulletin/android-multiple-vulnerabilities_20260303
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43766
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43859
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-2879
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-10865
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-13952
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-20760 (to CVE-2025-20762)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-20793 (to CVE-2025-20795)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-32313
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-38616
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-38618
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-39682
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-39946
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-40266
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-47339
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-47346
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-47348
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-47366
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-47378
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-47385
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-47388
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-47394 (to CVE-2025-47398)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-47402
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48544
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48567 (to CVE-2025-48568)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48574
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48577 (to CVE-2025-48579)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48582
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48585
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48587
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48602
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48605
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48609
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48613
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48619
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48630 (to CVE-2025-48631)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48634 (to CVE-2025-48635)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48641 (to CVE-2025-48642)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48644 (to CVE-2025-48646)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48650
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48653 (to CVE-2025-48654)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-58407 (to CVE-2025-58409)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-58411
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-59600
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-61612 (to CVE-2025-61616)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-64783 (to CVE-2025-64784)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-64893
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-69278 (to CVE-2025-69279)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-0005 (to CVE-2026-8)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-0010 (to CVE-2026-15)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-0017
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-0020 (to CVE-2026-21)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-0023 (to CVE-2026-32)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-0034 (to CVE-2026-35)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-0037 (to CVE-2026-38)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-0047
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-21735
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-20425 (to CVE-2026-20428)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-20434
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-20401 (to CVE-2026-20406)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-20420 (to CVE-2026-20422)
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-21385


Tag: Android
Tags