dbcve.org
AndroidOperating system · Google

CVE-2026-0012

MEDIUM · 6.2 CVSS v3.1 Published 2026-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
In setHideSensitive of ExpandableNotificationRow.java, there is a possible contact name leak due 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 confidence

A logic error in the setHideSensitive method of ExpandableNotificationRow.java in Android's notification system causes contact names to be disclosed even when sensitive content hiding is enabled. This allows local information disclosure of contact names without requiring any special privileges or user interaction.

MitigationApply the vendor patch for Android that corrects the logic in ExpandableNotificationRow.java's setHideSensitive method to properly hide contact names. Until the patch is available, users may need to adjust notification settings or limit sensitive app notifications.

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
AndroidOperating system
Affected:= 14.0= 15.0= 16.0

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Android version
    Go to Settings > About Phone > Android version, or run 'adb shell getprop ro.build.version.release'
    Affected if Version is 14.0, 15.0, or 16.0 exactly as listed in affected versions
  2. Verify sensitive notification hiding is enabled
    Navigate to Settings > Notifications > Sensitive notifications (or Settings > Privacy > Notifications on some devices). Confirm 'Hide sensitive content' or 'Hide notification content' is turned ON.
    Affected if The setting is enabled but contact names still appear in notifications from apps like Messages or third-party messaging apps
  3. Test notification display behavior
    Receive a notification from a known contact while sensitive content hiding is enabled. Observe whether the sender's name or contact name is visible in the notification preview on the lock screen or notification shade.
    Affected if Contact names are displayed despite sensitive content hiding being enabled - this indicates the vulnerability is present
  4. Check notification app settings
    Go to Settings > Apps > Messaging (or your default SMS app) > Notifications. Review whether 'Show sensitive content' or similar privacy options are configured correctly.
    Affected if Content is not being hidden as expected by the settings configuration

You are affected if your Android version is exactly 14.0, 15.0, or 16.0 and contact names appear in notifications even when sensitive content hiding is enabled in your notification settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for Android that corrects the logic in ExpandableNotificationRow.java's setHideSensitive method to properly hide contact names. Until the patch is available, users may need to adjust notification settings or limit sensitive app notifications.

Recommended fix Moderate confidence

Android Security Bulletin (monthly patch containing fix for setHideSensitive logic error in ExpandableNotificationRow)

  1. Check your Android device's current security patch level in Settings > About Phone > Security Patch Level
  2. Ensure your device receives the latest Android security update from your device manufacturer
  3. For AOSP/custom ROM users, upgrade to a build incorporating the fix in frameworks/base, specifically in ExpandableNotificationRow.java setHideSensitive method
  4. Verify the security patch level reflects the month containing the fix for CVE-2026-0012
Caveat Security updates typically have minimal breaking changes; some older apps relying on the previous notification behavior may be affected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,576.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0012 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0012 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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