CVE-2026-0080: Integer Overflow

Published Jun 1, 2026
·
Updated

In multiple functions of ubsanthrowingruntime.cpp, there is a possible way to cause a crash due to an integer overflow. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

Affected Software

7 affected components
llvm compiler-rt (UBSan runtime)
Google Android=14.0
Google Android=15.0
Google Android=16.0
Google Android=16.0-qpr2_beta_1
Google Android=16.0-qpr2_beta_2
Google Android=16.0-qpr2_beta_3

Event History

Jun 1, 2026
CVE Published
via MITRE·09:14 PM
Data Sourced
via MITRE·09:14 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-0080?

CVE-2026-0080 has a medium severity score of 6.5.

2

What software is affected by CVE-2026-0080?

CVE-2026-0080 affects Google Android and the llvm compiler-rt (UBSan runtime) from LLVM.

3

How do I fix CVE-2026-0080?

To fix CVE-2026-0080, ensure you are using the latest version of the affected software as it may contain patches for this vulnerability.

4

What type of vulnerability is CVE-2026-0080?

CVE-2026-0080 is categorized as an integer overflow vulnerability that can lead to a remote denial of service.

5

Does CVE-2026-0080 require user interaction for exploitation?

No, CVE-2026-0080 does not require user interaction to be exploited.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203