# CVE-2025-58486: Improper input validation in Samsung Account prior to version 15.5.01.1 allows local attacker to execute arbitrary script.


- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Dec 2025
- **Updated:** 2 Dec 2025
- **Also known as:** GHSA-r68g-vcqm-77rw

## What is CVE-2025-58486?

CVE-2025-58486 is a medium-severity vulnerability in Samsung Account, published on 2 Dec 2025. 

### Official description

Improper input validation in Samsung Account prior to version 15.5.01.1 allows local attacker to execute arbitrary script.

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

It affects 1 product.


Products: Samsung Account.

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

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

## Is CVE-2025-58486 being exploited?

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

## Other vulnerabilities in Samsung Account

- [CVE-2026-20994](https://insights.sbomify.com/CVE-2026-20994/): Open redirect in Samsung Account (medium 6.9)
- [CVE-2022-30735](https://insights.sbomify.com/CVE-2022-30735/): Privilege escalation in Samsung Account (medium 5.9)
- [CVE-2025-21076](https://insights.sbomify.com/CVE-2025-21076/): Missing authorization in Samsung Account (medium 5.5)
- [CVE-2023-42546](https://insights.sbomify.com/CVE-2023-42546/): Information disclosure in Samsung Account (medium 5.5)
- [CVE-2023-42547](https://insights.sbomify.com/CVE-2023-42547/): Information disclosure in Samsung Account (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58486 is a medium-severity vulnerability in Samsung Account, published on 2 Dec 2025. 
Exploitation: There is no known exploitation of CVE-2025-58486 in the wild and no public exploit code.

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

## Sources

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

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