dbcve.org
AndroidOperating system · Google

CVE-2026-0043

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In multiple functions of ubsan_throwing_runtime.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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Integer overflow vulnerability in multiple functions of LLVM's Undefined Behavior Sanitizer runtime (ubsan_throwing_runtime.cpp). The overflow can be exploited for persistent denial of service and local privilege escalation without requiring additional privileges or user interaction.

MitigationApply vendor patches for LLVM/Clang toolchain once available; in interim, restrict access to compiled binaries using the affected sanitizer and consider disabling ubsan in production environments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 14.0= 15.0= 16.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Android OS version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if The version is 14.0, 15.0, or 16.0
  2. Identify apps or libraries built with ubsan
    Search for libraries or APKs that were compiled with -fsanitize=undefined flag enabled during compilation. Check build logs for ubsan flags, or inspect compiled binaries for ubsan runtime references using 'strings <binary> | grep ubsan'
    Affected if Applications or system libraries on the device contain code compiled with the Undefined Behavior Sanitizer (ubsan) enabled
  3. Verify ubsan runtime is loaded
    Check running processes for ubsan runtime libraries: run 'ls /data/data/<package>/files/' or inspect process memory maps for libubsan.so or similar sanitizer runtime libraries
    Affected if The ubsan runtime library (libubsan) is present and loaded by any application on the device
  4. Determine LLVM/Clang toolchain version
    If you build applications locally, check the compiler version with 'clang --version' or 'llvm-config --version' used to compile the APKs
    Affected if The toolchain version matches the vulnerable LLVM releases that include the flawed ubsan_throwing_runtime.cpp code

A device is affected if it runs Android 14.0, 15.0, or 16.0 AND has applications or libraries compiled with ubsan enabled, which would load the vulnerable sanitizer runtime.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for LLVM/Clang toolchain once available; in interim, restrict access to compiled binaries using the affected sanitizer and consider disabling ubsan in production environments.

Recommended fix Moderate confidence

Latest Android Security Patch Level (monthly updates contain fixes for such vulnerabilities)

  1. Apply the latest Android Security Patch Level for your device. Go to Settings > Security > Security update and install any available updates.
  2. For Pixel devices, ensure the latest monthly platform update is installed via Settings > System > Software update > Check for updates
  3. Verify the patch level after updating: Go to Settings > About Phone > Android version and confirm the security patch level is newer than the vulnerable version
  4. If updates are not available from your device manufacturer, consider upgrading to a device that receives active security support
Caveat Security patches typically have minimal breaking changes; however, ensure backup of critical data before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0043 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0043 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data