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

11 affected componentsFixes available
llvm libubsan (compiler-rt)
Google Android
android/platform/external/dng_sdk>=17-next:0<17-next:2026-06-01
17-next:2026-06-01
android/platform/external/dng_sdk>=15:0<15:2026-06-01
15:2026-06-01
android/platform/external/dng_sdk>=16:0<16:2026-06-01
16:2026-06-01
android/platform/external/dng_sdk>=16-qpr2:0<16-qpr2:2026-06-01
16-qpr2:2026-06-01
android/platform/external/dng_sdk>=14:0<14:2026-06-01
14:2026-06-01
Google Android=14.0
Google Android=15.0
Google Android=16.0
Google Android=16.0-qpr2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade android/platform/external/dng_sdk to a version that resolves this vulnerability.

    Fixed in 17-next:2026-06-01
  2. Upgrade

    Upgrade android/platform/external/dng_sdk to a version that resolves this vulnerability.

    Fixed in 15:2026-06-01
  3. Upgrade

    Upgrade android/platform/external/dng_sdk to a version that resolves this vulnerability.

    Fixed in 16:2026-06-01
  4. Upgrade

    Upgrade android/platform/external/dng_sdk to a version that resolves this vulnerability.

    Fixed in 16-qpr2:2026-06-01
  5. Upgrade

    Upgrade android/platform/external/dng_sdk to a version that resolves this vulnerability.

    Fixed in 14:2026-06-01

Event History

Jun 1, 2026
CVE Published
via Android·12:00 AM
Advisory Published
via OSV·12:00 AM
Data Sourced
via Android·12:00 AM
SeverityWeaknessAffected Software
Data Sourced
via OSV·12:00 AM
DescriptionAffected Software
CVE Published
via MITRE·09:14 PM
Data Sourced
via MITRE·09:14 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeaknessAffected Software

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