dbcve.org
AndroidOperating system · Samsung

CVE-2026-21029

HIGH · 7.8 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 →
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 Galaxy Editing Service prior to SMR Jun-2026 Release 1 allows local attacker to execute privileged operations.

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 · high confidence

Improper export of Android application components in Samsung's Galaxy Editing Service allows any local application to interact with privileged components that should not be exposed. This enables a local attacker to bypass Android's sandbox and execute elevated operations that would normally require system-level or application-level privileges.

MitigationApply the vendor patch (SMR Jun-2026 Release 1 or later) to affected Samsung Galaxy devices. Organizations should verify device inventory for the Galaxy Editing Service and ensure the June 2026 security patch level is installed.

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. Verify Galaxy Editing Service is installed
    Use ADB command 'adb shell pm list packages | grep -i galaxy' or check device Settings > Apps for Galaxy Editing Service package
    Affected if The Galaxy Editing Service app is present on the device
  2. Check Galaxy Editing Service version
    Use ADB command 'adb shell dumpsys package com.samsung.android.app.galaxyediting' or view app info in Settings > Apps > Galaxy Editing Service
    Affected if Version equals 14.0, 15.0, or 16.0 (matching affected product versions)
  3. Verify Android OS version
    Check Settings > About Phone > Android version or use 'adb shell getprop ro.build.version.release'
    Affected if Device runs Android 14, Android 15, or Android 16 (the affected OS versions)
  4. Inspect app component exports
    Decompile the APK and examine AndroidManifest.xml for exported='true' on privileged components, or use 'adb shell dumpsys package com.samsung.android.app.galaxyediting' to list exported activities/services
    Affected if Galaxy Editing Service exposes privileged components with exported="true" that should require system privileges

The device is affected if Galaxy Editing Service is installed with version 14.0, 15.0, or 16.0 on a device running Android 14, 15, or 16, and the app exposes privileged components that should be protected by Android's sandbox.

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 (SMR Jun-2026 Release 1 or later) to affected Samsung Galaxy devices. Organizations should verify device inventory for the Galaxy Editing Service and ensure the June 2026 security patch level is installed.

Recommended fix Moderate confidence

SMR Jun-2026 Release 1 (Samsung Mobile Security Maintenance Release)

  1. Identify your Samsung device model and current Android version (Settings > About Phone > Android version)
  2. Check for system updates: Go to Settings > Software update > Download and install
  3. Ensure the device updates to SMR Jun-2026 Release 1 or later which contains the fix for Galaxy Editing Service improper component export
  4. Verify the update was applied by checking Settings > About Phone > Software information > Security patch level
Caveat Samsung monthly security updates typically have no breaking changes; standard user data is preserved

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 / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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