CVE-2025-48556: Android Framework Base NotificationChannel Desynchronization Vulnerability

platform/frameworks/base Updated 02 Oct 2025

Summary

01/09/2025
Yes i
High
Not published

CVE-2025-48556: In multiple methods of NotificationChannel.java, there is a possible desynchronization from persistence due to improper input validation. Affects platform/frameworks/base across 3 version ranges.

>= 15:0, < 15:2025-09-01 >= 16:0, < 16:2025-09-01 >= 16-next:0, < 16-next:2025-09-01

Fixed in 16-next:2025-09-01. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Android Framework Base package is a core component of the Android operating system, responsible for providing essential functionalities and APIs for application development. It includes various classes and methods that facilitate app notifications, among other features. The NotificationChannel class specifically manages notification channels, allowing developers to customize notification behaviors for their applications. This package is critical for ensuring that notifications are delivered and displayed correctly to users.

Vulnerability Detail

In multiple methods of NotificationChannel.java, there is a possible desynchronization from persistence due to improper input validation. This vulnerability can lead to local escalation of privilege, allowing an attacker to gain unauthorized access to certain functionalities without requiring additional execution privileges. User interaction is necessary for exploitation, making it a potential risk in environments where users may be tricked into executing malicious actions.

How To Fix

Minimum fixed version

16-next:2025-09-01

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, ensure that user input is thoroughly validated before processing it in the NotificationChannel methods. Implement additional checks to prevent unauthorized access and desynchronization issues.

Conclusion

CVE-2025-48556 represents a significant vulnerability within the Android Framework Base package, specifically affecting the NotificationChannel class. It is crucial for developers to apply the necessary patches and implement workarounds to protect their applications from potential exploitation.

See every vulnerability recorded for platform/frameworks/base →

Share this vulnerability

FAQ

CVE-2025-48556 is a vulnerability in the Android Framework Base package that allows for local escalation of privilege due to improper input validation in the NotificationChannel class.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities. Check your application against CVE-2025-48556 using the Vulert playground at Vulert Scanner without needing to sign up.

The vulnerability can lead to unauthorized access to certain functionalities within the application, potentially compromising user data and application integrity.

Yes, user interaction is necessary for the exploitation of this vulnerability, as an attacker may need to trick the user into executing malicious actions.

If immediate updates are not possible, implement input validation and additional security checks as a temporary workaround to mitigate the risks associated with this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for platform/frameworks/base.

How To Fix

Minimum fixed version

16-next:2025-09-01

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback