dbcve.org
AndroidOperating system · Samsung

CVE-2026-21020

HIGH · 7.8 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 export of android application components in OmaCP prior to SMR May-2026 Release 1 allows local attackers to trigger privileged functions.

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

This is an improper export vulnerability in Android application components (Activities, Services, Broadcast Receivers, or Content Providers) within OmaCP. The flaw allows local applications on the device to invoke privileged functions that should not be exposed, potentially leading to unauthorized access or privilege escalation.

MitigationProperly configure AndroidManifest.xml to restrict component exports using permissions or removing unnecessary exports, and apply the SMR May-2026 Release 1 patch.

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

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

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 and verify if the version is 14.0, 15.0, or 16.0
    Affected if The device runs Android 14.0, 15.0, or 16.0 on a Samsung device
  2. Identify OmaCP application
    Check installed applications on the device for an app named OmaCP, OMA CP, or similar Samsung OMA-related component (typically found in Settings > Apps > Show system apps)
    Affected if OmaCP application is present on the device
  3. Inspect exported components
    Use a tool like 'aapt dump badging' on the OmaCP APK or inspect the AndroidManifest.xml for exported Activity, Service, BroadcastReceiver, or ContentProvider components
    Affected if OmaCP has any of its components (Activities, Services, Broadcast Receivers, or Content Providers) marked as exported in the manifest
  4. Verify component permissions
    Examine whether exported components require any permissions to invoke, or if they are unprotected allowing any local application to access them
    Affected if Exported components do not require signature-level or dangerous permissions and can be invoked by arbitrary local applications

A Samsung Android device running version 14.0, 15.0, or 16.0 with the OmaCP application installed and having unprotected exported components is affected by this vulnerability.

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

Properly configure AndroidManifest.xml to restrict component exports using permissions or removing unnecessary exports, and apply the SMR May-2026 Release 1 patch.

Recommended fix High confidence

SMR May-2026 Release 1 or later

  1. Check your Samsung device's current Android version (Settings > About Phone > Android version)
  2. Check your device's current SMR (Samsung Maintenance Release) version (Settings > About Phone > Software info > Maintenance release version)
  3. Navigate to Settings > Software update > Download and install to check for available updates
  4. If an update is available, download and install the SMR May-2026 Release 1 or later
  5. After updating, verify the fix by confirming the SMR version reflects May-2026 Release 1 or newer

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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