# CVE-2026-21074: Privilege escalation in Bixby

> Local attackers can execute arbitrary commands with Bixby privileges due to incorrect default permissions in Samsung Bixby.

- **Severity:** High 7.2 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-2xcm-9h5p-f5jp

## What is CVE-2026-21074?

CVE-2026-21074 is a high-severity vulnerability in Samsung Mobile Bixby, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect default permissions in Bixby prior to version 4.0.86.0 allows local attackers to execute arbitrary commands with Bixby privilege.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2026-21074?


## How do I fix CVE-2026-21074?

No fix has been published for CVE-2026-21074 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-21074 being exploited?

There is no known exploitation of CVE-2026-21074 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-21074 and fix it if it is affected.

What it is: CVE-2026-21074 is a high-severity vulnerability in Samsung Mobile Bixby, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-21074 in the wild and no public exploit code.

Affected product: Samsung Mobile Bixby. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-21074/ (Markdown: https://insights.sbomify.com/CVE-2026-21074/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-21074
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-21074
- OSV: https://osv.dev/vulnerability/CVE-2026-21074

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-21074/
Summaries are generated and may contain mistakes; the official description above is the record.