LiveActive security incident?Get immediate response
CVE Record

CVE-2025-48543: In multiple locations, there is a possible way to escape chrome sandbox to attack android system_server due...

In multiple locations, there is a possible way to escape chrome sandbox to attack android system_server due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

HighCVSS 8.8Known exploitedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-48543 is a high-impact Android flaw that can let code already running with low privileges escape the Chrome sandbox and reach Android’s system_server. That can give an attacker broad control over device confidentiality, integrity, and availability. CISA lists it in KEV, so treat it as exploited in the wild.

Executive priority

Treat this as an urgent mobile fleet remediation item. CISA KEV status indicates real-world exploitation, and successful exploitation could move from a sandboxed context into a privileged Android system process. Patch availability and device support should drive immediate risk decisions.

Technical view

The issue is a CWE-416 use-after-free in Android, described across multiple locations. It enables local escalation of privilege from the Chrome sandbox to system_server with low privileges and no user interaction. CVSS is 8.8, with changed scope and high confidentiality, integrity, and availability impact.

Likely exposure

Android fleets running Android 13, 14, 15, or 16 before the relevant September 2025 Android security update may be exposed. Exposure depends on OEM and carrier patch delivery. The provided sources do not identify specific device models, Chrome versions, or enterprise configurations that change risk.

Exploitation context

Active exploitation is supported by CISA KEV listing. The public bundle does not provide exploit mechanics, attacker tooling, observed campaigns, or indicators. The vulnerability requires local execution privileges but no user interaction, which raises urgency for already-compromised apps or chained mobile attacks.

Researcher notes

The source bundle supports affected Android versions, CWE-416, CVSS 8.8, and KEV status. It does not provide exploit details, affected device models, or complete remediation nuances beyond the Android bulletin and referenced code change. Avoid assuming browser-only exposure without vendor confirmation.

Mitigation direction

  • Apply Android September 2025 security updates or vendor-equivalent OTA patches.
  • Prioritize Android 13 through 16 devices in managed fleets.
  • Check OEM and carrier guidance for device-specific patch availability.
  • Restrict or retire devices that cannot receive the required update.
  • Monitor CISA KEV due dates and internal remediation SLAs.

Validation and detection

  • Inventory Android devices by OS version and security patch level.
  • Confirm patch levels include the September 2025 Android bulletin fix.
  • Verify OEM advisories for each managed device family.
  • Use MDM compliance policies to flag unpatched Android 13-16 devices.
  • Track exceptions for unsupported or delayed-update devices.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-48543 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
Yes
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H26Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2025-48543Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid16, 15, 14, 13unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.