Skip to main content

Samsung Bixby EUVDEUVD-2026-112562

| CVE-2026-21157 HIGH
2026-10-29 SamsungMobile GHSA-pw33-6fpc-cwfm
8.3
CVSS 4.0 · Vendor: SamsungMobile
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain privileged local foothold on device
  2. Delivery
    Send crafted input to Bixby component
  3. Exploit
    Trigger improper input validation
  4. Execution
    Launch arbitrary activity with Bixby's context
  5. Impact
    Access or alter protected data/functions

Vulnerability Assessment

Exploitation Conditions

Requires an attacker who already holds high local privileges (PR:H) on a Samsung device running Bixby prior to version 4.0.85.6; the flaw is reached by supplying unvalidated input to the Bixby component to launch an arbitrary activity. No user interaction is required (UI:N), but exploitation is strictly local (AV:L) and gated by the need for pre-existing elevated privileges - there is no remote or unauthenticated path, and the specific feature/interface exposing the unvalidated input is not detailed in the available sources. The only complete fix stated by the vendor is updating Bixby to 4.0.85.6 or later.

Impact

This is a genuine but bounded risk rather than an internet-facing emergency. The supplied CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:H/UI:N, VC:H/VI:H/VA:L, score 8.3) describes a locally exploitable flaw that requires high privileges, low attack complexity, and no user interaction, with high confidentiality and integrity impact and limited availability impact confined to the vulnerable system (SC:N/SI:N/SA:N). The vuln.today decision label is 'this_week', indicating prompt but not immediate ('act_now'/'emergency') remediation urgency. There is no CISA KEV entry, no EPSS probability supplied, and no proof-of-concept or exploit reference in the provided data, so there is no public exploit identified at time of analysis. The requirement for pre-existing high privileges (PR:H) is the dominant limiting factor: an attacker must already hold a privileged local position on the device, which substantially narrows realistic exploitation to malicious or already-compromised privileged apps/processes rather than remote or drive-by attacks. Note a labeling tension: the Tags include 'Information Disclosure', but the description ('allows privileged local attackers to launch arbitrary activity') and the vector's VC:H AND VI:H both point to an integrity/activity-launch impact beyond pure disclosure - treat the impact as both confidentiality and integrity.

Exploit ScenarioDerived

A malicious or compromised app running with high privileges on a Samsung device passes crafted/unvalidated input to Bixby, which fails to properly validate it and launches an attacker-chosen activity. Because exploitation needs no user interaction and low complexity, a privileged local process could trigger it silently; no public exploit code is identified at this time.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 29, 2026

Improper input validation in Samsung Bixby before version 4.0.85.6 allows a local attacker who already holds high privileges on the device to launch arbitrary activities, giving a high impact on confidentiality and integrity and a limited impact on availability. Exploitation is strictly local and gated behind pre-existing elevated privileges, with no user interaction required and no remote or unauthenticated path described in the available sources. No public exploit code has been identified at time of analysis, the issue is not listed in CISA KEV, and the vendor-reported severity is high (CVSS 8.3) while our assessed CVSS 3.1 vector is 6.5-class local, high-privilege impact; vuln.today prioritizes it as a this-week item rather than an emergency.

RemediationAI

Vendor-released patch: Bixby 4.0.85.6. Samsung states that updating Bixby to version 4.0.85.6 or later is the fix, and this is the only complete remediation the advisory describes; administrators and device owners should verify the installed Bixby version through the Galaxy Store or the device's application settings and push the update through their normal device management channel. No workaround, feature toggle or configuration-based mitigation is documented in the supplied advisory, so the fix should be treated as version-gated rather than configurable, and the residual exposure until devices are updated is limited to callers that already hold high local privileges. Full details and the vendor's bulletin are at https://security.samsungmobile.com/serviceWeb.smsb?year=2026&month=07.

Affected VersionsENISA

Bixby patch: 4.0.85.6

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Bixby is Samsung's on-device voice assistant that runs with system-level reach into Samsung Android devices, which is why the affected package is tracked under CPE cpe:2.3:a:samsung_mobile:bixby:*:*:*:*:*:*:*:* with all versions below 4.0.85.6 in scope. No CWE identifier was assigned in the supplied data, but the reported weakness is a failure to validate input before it is consumed by the Bixby component, which then permits the launch of arbitrary activities. The presence of PR:H in both the vendor CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L) and our assessed CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L) means the flaw is only reachable by a caller that already possesses high local privileges on the device; the vector does not encode any remote, network-adjacent or unauthenticated route. The trigger is not described in the available sources - the specific Bixby feature, intent handler or interface that accepts the unvalidated input is not disclosed, and the SSVC-style decision signal (this_week) plus the absence of KEV and of any EPSS value mean the practical risk is bounded by the local, high-privilege prerequisite rather than by exposure to the internet.

Know when Bixby gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (SamsungMobile) PRIMARY 8.3 HIGH
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
vuln.today AI 6.3 MEDIUM

Local vector and PR:H because exploitation needs pre-existing privileged local access; AC:L and UI:N per vendor data; C:H/I:H from arbitrary activity launch, A:L for limited availability impact.

3.1 AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
4.0 AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (SamsungMobile).

CVSS VectorVendor: SamsungMobile

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Improper input validation in Bixby prior to version 4.0.85.6 allows privileged local attackers to launch arbitrary activity.

Executive ViewAI

Why It Matters

CVE-2026-21157 in Samsung Bixby could allow a local attacker with high privileges to launch arbitrary activities, potentially compromising confidentiality and integrity. However, exploitation requires pre-existing elevated privileges, limiting the threat to scenarios where an attacker already has significant control. Leadership should monitor for patches and ensure privileged access is tightly controlled.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting local high-privilege access, monitoring for suspicious activity from privileged accounts, and applying least-privilege policies.

Threat Intelligence Overview

Prevalence
High
Bixby is Samsung's preinstalled assistant on a very large Galaxy install base
Social Media
1
Sightings
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS N/A
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Medium

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy