# CVE-2025-21065: Privilege escalation in Retail Mode

> Improper input validation in Samsung Retail Mode allows attackers to execute privileged commands on their own devices.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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 Oct 2025
- **Updated:** 10 Oct 2025
- **Also known as:** GHSA-vw25-h68c-8mm4

## What is CVE-2025-21065?

CVE-2025-21065 is a medium-severity vulnerability in Samsung Mobile Retail Mode, published on 10 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper input validation in Retail Mode prior to version 5.59.11 allows self attackers to execute privileged commands on their own devices.

## Which versions are affected by CVE-2025-21065?


## How do I fix CVE-2025-21065?

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

## Is CVE-2025-21065 being exploited?

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

Public exploit code:

- A PoC for CVE-2025-21065 that allows any self-attacker to execute commands with Retail Mode privileges (UID 1000/GID 1000, u:r:system_app:s0) (github_poc): https://github.com/Pealeap/CVE-2025-21065

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-21065 and fix it if it is affected.

What it is: CVE-2025-21065 is a medium-severity vulnerability in Samsung Mobile Retail Mode, published on 10 Oct 2025. 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-2025-21065 in the wild and no public exploit code.

Affected product: Samsung Mobile Retail Mode. 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-2025-21065/ (Markdown: https://insights.sbomify.com/CVE-2025-21065/index.md)
```

## Sources

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

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