Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Integer overflow in Android System ubsan_throwing_runtime.cpp leading to local privilege escalation

IdentifiersCVE-2026-0043CWE-190· Integer Overflow or Wraparound

CVE-2026-0043 is a critical vulnerability in the Android System component. According to the provided content, the flaw exists in multiple functions of ubsan_throwing_runtime.cpp and is caused by an integer overflow. The issue can result in a persistent denial of service and, under exploitation, could also lead to local escalation of privilege. The bulletin context classifies it as a System elevation-of-privilege issue and states that exploitation does not require user interaction or additional execution privileges.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may allow an attacker to trigger a persistent denial of service on the affected device and potentially achieve local privilege escalation. The Android bulletin context further indicates that the vulnerability is considered critical because it could enable elevation of privilege in the System component without requiring user input or pre-existing elevated execution privileges.

Mitigation

If you can’t patch tonight, do this now.

If patching cannot be applied immediately, mitigation information specific to this vulnerability is not provided in the supplied content. General risk reduction would consist of limiting installation and execution of untrusted local code, maintaining Google Play Protect and equivalent application control mechanisms, and accelerating deployment of OEM security updates, but no vulnerability-specific mitigation is currently available from the provided material.

Remediation

Patch, then assume compromise.

Apply the Android security updates that include the June 2026 Android security bulletin fixes for CVE-2026-0043. The provided content indicates that Google addressed this issue in the June 2026 Android security release, with fixes available through the relevant Android security patch levels. Deploy vendor/OEM updates incorporating the corresponding Android System patch.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.