CVE-2025-48572

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Android Framework. For every flaw being used in attacks, see Exploited flaws; for Android’s, see Android flaws being used in attacks.

CVE-2025-48572 is a security flaw in Android Framework, Google’s operating system for phones and tablets. Someone who already has a foothold can use Android Framework to take full control of the machine. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 2 Dec 2025.[1]

Android Framework is in things households have, such as phones, computers, browsers and everyday apps, so the fix matters at home as much as at work. Android has published a fix or advice.

Description

CISA calls it a privilege escalation in Android Framework. In its words: “Android Framework contains an unspecified vulnerability that allows for privilege escalation.”[1]

The CVE record adds: “In multiple locations, there is a possible way to launch activities from the background due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.”[2]

The underlying weakness is missing authentication (CWE-306), in MITRE’s list of common software weaknesses.

It scores 7.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by the organisation that published the CVE using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it; Android’s advisory has them[3]. CISA names the product as Android Framework.

Every device with Android Framework needs the update.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 2 Dec 2025. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 23 Dec 2025 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at under 1%. That’s in the top 83% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Android has published a fix or advice.[3] CISA’s required action: “Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.”[1]

  1. Update Android Framework now.On Android: Settings, then System or Software update. Phones only get these fixes while their maker still supports them. Then turn on automatic updates, so the next fix arrives on its own.
  2. If there’s no update, stop using it.CISA’s advice when a flaw being used in attacks has no fix is to stop using the product until it does.

Timeline

DateEvent
CISA adds it to its catalog of flaws known to be used in attacks.[1]
The flaw is made public in the National Vulnerability Database, with a severity score of 7.8.[2]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at under 1%.[4]

See also

Other Android Framework flaws

Other Android flaws

Other missing authentication flaws

  • CVE-2026-111357, Ivanti Connect Secure: missing authentication for critical function ·
  • CVE-2026-67277, MikroTik RouterOS: missing authentication for critical function ·
  • CVE-2026-81578, PaperCut NG/MF: missing authentication for critical function ·
  • CVE-2026-72529, TrueConf Server: missing authentication for critical function ·
  • CVE-2026-56164, Microsoft SharePoint Server: missing authentication for critical function ·

Added the same day

  • CVE-2025-48633, Android Framework: information disclosure ·

Every Android flaw on CISA’s list · Everything added in December 2025

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Android Framework Privilege Escalation Vulnerability”. Known Exploited Vulnerabilities Catalog, added 2 Dec 2025.
  2. ^ National Institute of Standards and Technology. “CVE-2025-48572 Detail”. National Vulnerability Database, published 8 Dec 2025.
  3. ^ Android. Advisories and fixes: source.android.com, source.android.com.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.003, percentile 17.6, 31 Oct 2026.
  5. CVE Program. “CVE-2025-48572”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.