# CVE-2026-21129: Missing authorization in Samsung Checkout

> Local attackers can launch arbitrary activities with elevated privileges due to improper input validation in Samsung Checkout.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-x2cq-w578-xxmh

## What is CVE-2026-21129?

CVE-2026-21129 is a medium-severity missing authorization vulnerability in Samsung Checkout, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper input validation in GuestCreditCardRegisterActivity of Samsung Checkout prior to version 5.1.03.1 allows local attackers to launch an arbitrary activity with Samsung Checkout privileges.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-21129 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-21129 is a medium-severity missing authorization vulnerability in Samsung Checkout, published on 12 Oct 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-21129 in the wild and no public exploit code.

Affected product: Samsung Checkout. 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-21129/ (Markdown: https://insights.sbomify.com/CVE-2026-21129/index.md)
```

## Sources

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

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