CVE-2026-0043: Integer Overflow

Published Jun 1, 2026
·
Updated

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

Affected Software

7 affected components
llvm libubsan (compiler-rt)
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

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Restrict local access to systems that include the UBSan runtime (ubsan_throwing_runtime). Limit which accounts can log in or execute binaries on affected hosts (remove unneeded local accounts, enforce sudo/privilege restrictions), and apply host-based ACLs to prevent untrusted users from reaching those systems.

  2. Compensating control

    Isolate affected hosts from untrusted networks and users using network segmentation, host firewalls, and access control lists. Block or limit management and local-access services to trusted admin networks only.

  3. Operational

    Monitor and investigate signs of persistent denial-of-service and local privilege escalation on affected systems (review logs, crash reports, and unusual process behavior). If compromise is suspected, perform incident response actions such as isolating the host, rebuilding or restoring from known-good backups, and rotating any potentially exposed credentials.

  4. Operational

    Apply vendor-supplied fixes or patches for the vulnerable UBSan runtime as soon as they are released; plan for prompt testing and deployment of updates to affected systems.

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-0043?

The severity of CVE-2026-0043 is medium with a score of 5.5 according to the CVSS 3.1 system.

2

What is the risk associated with CVE-2026-0043?

The risk associated with CVE-2026-0043 is classified as 32.

3

How do I fix CVE-2026-0043?

To fix CVE-2026-0043, you should apply the latest security updates provided for Google Android and llvm libubsan.

4

What vulnerabilities are present in CVE-2026-0043?

CVE-2026-0043 contains a vulnerability due to an integer overflow that can lead to persistent denial of service.

5

Is user interaction required to exploit CVE-2026-0043?

No, user interaction is not needed for the exploitation of CVE-2026-0043.

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