CVE-2025-22421
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn contentDescForNotification of NotificationContentDescription.kt, there is a possible notification content leak through the lockscreen due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA logic error in the contentDescForNotification function in NotificationContentDescription.kt causes notification content to be incorrectly displayed on the lock screen when it should be hidden. This allows sensitive notification content (such as message previews, OTPs, or other confidential information) to be visible to anyone with physical access to the locked device, resulting in local information disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 13.0= 14.0= 15.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Android versionNavigate to Settings > About Phone > Android version. Alternatively, run 'adb shell getprop ro.build.version.release' via Android Debug Bridge.Affected if The version is 13.0, 14.0, or 15.0
-
Verify lock screen notification settingNavigate to Settings > Notifications > Notifications on lock screen. Check if this is set to Show all notification content or Show sensitive content only.Affected if Lock screen notifications are enabled and set to show content
-
Check sensitive notification filter settingNavigate to Settings > Notifications > Sensitive notification. Verify if this is disabled or set to show sensitive content on the lock screen.Affected if Sensitive notification filtering is disabled or allows sensitive content visibility on lock screen
-
Test notification behavior with sensitive contentReceive a notification containing potential sensitive information (such as an SMS with a verification code) while the device is locked. Observe whether the sensitive content (message preview, OTP) is visible on the lock screen when it should be hidden.Affected if Sensitive notification content (OTP, message preview, private data) is visible on the lock screen despite privacy settings intended to hide it
You are affected if your Android device runs version 13.0, 14.0, or 15.0 AND lock screen notifications are enabled with sensitive content set to display, allowing private notification data to be visible to anyone with physical access to the locked device.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataFix the logic error in the contentDescForNotification function to properly filter sensitive notification content from being displayed on the lock screen. This is a code-level fix in the Android System UI framework.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22421 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22421 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data