dbcve.org
AndroidOperating system · Samsung

CVE-2026-21028

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Improper access control in AuditLogService prior to SMR Jun-2026 Release 1 allows local attackers to access sensitive information.

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

Improper access control in AuditLogService allows local attackers to bypass authorization checks and access sensitive audit log information. The vulnerability exists in versions prior to SMR Jun-2026 Release 1, where the service fails to properly validate user permissions before returning log data.

MitigationUpgrade to SMR Jun-2026 Release 1 or later to obtain the access control fix. If immediate patching is not possible, restrict local device access to trusted applications only.

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:= 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
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 checks

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

  1. Identify Android version
    Go to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADB
    Affected if Android version is 16.0 (exact match)
  2. Check SMR (Samsung Maintenance Release) version
    Go to Settings > About Phone > Software information > Build number, or run 'getprop ro.build.version.sem' via ADB
    Affected if SMR version is earlier than Jun-2026 Release 1 (e.g., May-2026 or earlier)
  3. Verify AuditLogService presence
    Run 'dumpsys' via ADB to list running services and search for AuditLogService, or check /system/bin/ for the auditlog service binary
    Affected if AuditLogService is present and running on the device
  4. Check AuditLogService permissions
    Run 'dumpsys package <auditlog_service_pkg>' via ADB to inspect the service's permission configuration and exported status
    Affected if Service is exported without proper permission checks or allows unauthorized access
  5. Test AuditLogService access
    Use a local app or ADB command to query the AuditLogService API endpoint (if known) without valid credentials
    Affected if Service returns sensitive audit log data without authorization validation

Device is affected if running Samsung Android 16.0 with an SMR version earlier than Jun-2026 Release 1 and the AuditLogService is accessible without proper authorization enforcement.

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

Upgrade to SMR Jun-2026 Release 1 or later to obtain the access control fix. If immediate patching is not possible, restrict local device access to trusted applications only.

Recommended fix Moderate confidence

SMR Jun-2026 Release 1 (Android 16.0 with June 2026 security patch)

  1. 1. Verify the current Android version on the Samsung device is 16.0
  2. 2. Check for and install the latest system update (SMR Jun-2026 Release 1 or later)
  3. 3. Navigate to Settings > About Phone > Software Update on Samsung Android devices
  4. 4. Ensure the device is connected to Wi-Fi and has sufficient battery before updating
  5. 5. After update installation, verify the Security/MediaTek patch level reflects June 2026 or later in Settings > About Phone > Software Information
Caveat Standard Samsung software update; no expected breaking changes for end users

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21028 — 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-21028 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