Skip to main content
CVE-2023-48425VulnerabilityPublished Updated

CVE-2023-48425: Google Android · Remote code execution

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Dec 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

AI-suggested

Given the absence of official patches at the time of reporting, European organizations should implement a multi-layered mitigation strategy. First, conduct an inventory to identify all Android SoC devices in use, prioritizing those in critical roles. Limit network exposure of vulnerable devices by segmenting them in isolated network zones and applying strict firewall rules to restrict inbound traffic to trusted sources only. Employ network intrusion detection and prevention systems (IDS/IPS) with updated signatures to detect anomalous activities targeting U-Boot or bootloader exploitation attempts. Enforce strict device management policies, including disabling unnecessary network services and enforcing strong authentication mechanisms where applicable. Monitor vendor communications closely for patch releases and apply updates promptly once available. Additionally, consider deploying endpoint detection and response (EDR) solutions capable of detecting low-level firmware tampering or unusual bootloader behavior. For high-risk environments, evaluate the feasibility of replacing vulnerable hardware or using alternative secure boot mechanisms. Finally, train security teams to recognize signs of bootloader compromise and establish incident response plans tailored to firmware-level attacks.

Description

U-Boot vulnerability resulting in persistent Code Execution

References

Community reviews

Loading reviews…