CVE-2026-0040
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 · uneditedIn multiple functions of ubsan_throwing_runtime.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.
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 confidenceAn integer overflow vulnerability exists in multiple functions of the Undefined Behavior Sanitizer (UBSan) runtime library (ubsan_throwing_runtime.cpp). This flaw can be exploited to cause a crash resulting in remote denial of service, requiring no authentication or user interaction.
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= 14.0= 15.0= 16.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Android OS versionRun 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if Version is 14.0, 15.0, or 16.0 exactly (note: the affected versions are = meaning specific versions, not ranges)
-
Determine if UBSan is enabled in the buildCheck build configuration files (e.g., Android.mk, CMakeLists.txt) for '-fsanitize=undefined' flag, or check if the libubsan library is present on the device in /system/lib64 or /system/libAffected if UBSan is compiled into the system or application binaries
-
Identify UBSan runtime componentsSearch for ubsan_throwing_runtime.cpp or libubsan.so on the device. Use 'find /system -name '*ubsan*' 2>/dev/null' to locate UBSan-related librariesAffected if UBSan runtime libraries (libubsan) are present and loaded at runtime
You are affected if your Android device runs version 14.0, 15.0, or 16.0 AND the UBSan runtime libraries are present and active on the system.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the LLVM/Clang toolchain to a version containing the patched UBSan runtime, or temporarily disable UBSan in affected builds if an update is not immediately feasible.
Latest Android security update for your Android version (14.0, 15.0, or 16.0)
- Check your current Android security patch level in Settings > About Phone > Android version
- Apply the latest Android security update for your Android 14, 15, or 16 device
- For Pixel devices, check for and install available system updates
- For other device manufacturers, check with your carrier or manufacturer for the latest security patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0040 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0040 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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