dbcve.org
VulnerabilityAwaiting classification

CVE-2026-21055

HIGH · 8.5 CVSS v4.0 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
No privileges Zero-click 6 weeks old

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 Bixby prior to version 4.0.70.8 allows local attackers to execute arbitrary commands with Bixby privilege.

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 Samsung's Bixby voice assistant application for Android. The application's components (likely activities, services, or broadcast receivers) are exported without proper access controls, allowing a local malicious application to invoke these components and execute arbitrary commands with Bixby's elevated system privileges.

MitigationUpdate Bixby to version 4.0.70.8 or later. For enterprise mobile device management, ensure Bixby updates are pushed to managed devices and consider restricting Bixby installation on sensitive devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Bixby is installed
    Open Android Settings > Apps and search for 'Bixby', or use ADB command: `adb shell pm list packages | grep bixby`
    Affected if Bixby package is present on the device
  2. Identify the installed Bixby version
    Open Google Play Store, search for Bixby, and view the installed version from the app listing, or use ADB: `adb shell dumpsys package com.samsung.android.bixby.agent` and look for versionName
    Affected if A version number is returned from the package manager
  3. Compare installed version against fixed release
    Review the version identified in step 2. The fixed version is 4.0.70.8. Compare numerically: any version below 4.0.70.8 (including 4.0.x versions below .70.8 and all earlier major versions) is vulnerable
    Affected if Installed version is less than 4.0.70.8
  4. Verify Bixby has elevated system privileges
    Use ADB to inspect Bixby's declared permissions: `adb shell dumpsys package com.samsung.android.bixby.agent | grep -i permission`. Look for privileged system permissions granted to the application
    Affected if Bixby holds system-level or elevated privileges (such as INSTALL_PACKAGES, SYSTEM_ALERT_WINDOW, or shell-level access)

The device is affected if Bixby is installed with any version lower than 4.0.70.8 and the application holds elevated system privileges that could be exploited by a malicious local application through improperly exported components.

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 Bixby to version 4.0.70.8 or later. For enterprise mobile device management, ensure Bixby updates are pushed to managed devices and consider restricting Bixby installation on sensitive devices.

Recommended fix High confidence

Bixby version 4.0.70.8 or later

  1. Open the Galaxy Store app on your Samsung device
  2. Search for Bixby or navigate to the Updates section
  3. Update Bixby to version 4.0.70.8 or later
  4. Alternatively, go to Settings > Apps > Bixby and check for updates
  5. After updating, verify the installed version in Settings > Apps > Bixby > App info

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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