dbcve.org
AndroidOperating system · Samsung

CVE-2026-21026

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 export of android application components in SpriteWallpaper prior to SMR Jun-2026 Release 1 allows local attackers to access to 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

This is an Android component export vulnerability in SpriteWallpaper where application components (activities, services, broadcast receivers, or content providers) are improperly exported without adequate protection. This allows local attackers (with physical device access or a malicious local app) to interact with these components and access sensitive information that should be protected.

MitigationUpdate to SMR Jun-2026 Release 1 or later. For components that don't require external interaction, set android:exported="false" in the AndroidManifest.xml. For components that must be exported, implement proper permission checks and authentication.

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. Check if SpriteWallpaper app is installed
    Open Settings > Apps > Apps and search for 'SpriteWallpaper' or use adb command: adb shell pm list packages | grep sprite
    Affected if SpriteWallpaper package is present on the device
  2. Verify Samsung Android version is 16.0
    Go to Settings > About Phone > Android version or use adb command: adb shell getprop ro.build.version.release
    Affected if Version displays as 16.0 (Samsung Android) and matches affected range
  3. Inspect SpriteWallpaper AndroidManifest.xml for exported components
    Use adb to pull and inspect the manifest: adb shell pm path com.spritewallpaper.app && adb pull <path>/AndroidManifest.xml; then search for android:exported="true" attributes on activity, service, receiver, or provider tags
    Affected if Any sensitive component (activity, service, receiver, or provider) has android:exported="true" without proper permission checks
  4. Check exported components for protection levels
    In the AndroidManifest.xml, examine each exported component for android:permission attribute or intent-filter definitions; look for components allowing unauthorized access to sensitive data or functionality
    Affected if Exported components lack android:permission protection or allow unauthenticated access to sensitive features

User is affected if running Samsung Android 16.0 with SpriteWallpaper installed and the app has components exported without proper permission checks in its manifest.

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

Update to SMR Jun-2026 Release 1 or later. For components that don't require external interaction, set android:exported="false" in the AndroidManifest.xml. For components that must be exported, implement proper permission checks and authentication.

Recommended fix Moderate confidence

SMR Jun-2026 Release 1 (June 2026 Samsung Security Patch)

  1. Apply the Samsung SMR Jun-2026 Release 1 security update to your device
  2. Go to Settings > Software update > Download and install
  3. Ensure the update is fully installed before using SpriteWallpaper
Caveat None expected - this is a routine security patch

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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