What is CVE-2026-21055?
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.
1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 126 days ago.
Severity and exploitation probability
- CVSS v4.0 base score
- 8.5 — High (derived from score)
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 - EPSS (FIRST)
- 0.1% probability of exploitation in the next 30 days, higher than 5.6% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 6.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-07-10
Is CVE-2026-21055 being exploited?
Weaponised exploit code for CVE-2026-21055 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 21 in the Threadlinqs vulnerability feed.
Affected products and versions
- Samsung Mobile: Bixby
How to fix CVE-2026-21055
No vendor patch reference has been recorded for CVE-2026-21055 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-21055
1 tracked threat in the Threadlinqs corpus references CVE-2026-21055, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS, public proof-of-concept repositories.