# CVE-2025-20970: Missing authorization in Bixby Vision

> Local attackers can access image files with Bixby Vision privileges due to improper access control in Samsung Android devices.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A: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:** 7 May 2025
- **Updated:** 7 May 2025
- **Also known as:** GHSA-jg34-99pf-2cmp

## What is CVE-2025-20970?

CVE-2025-20970 is a medium-severity missing authorization vulnerability in Samsung Mobile Bixby Vision, published on 7 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control in Bixby Vision prior to version 3.8.1 in Android 13, 3.8.3 in Android 14, 3.8.21 in Android 15 allows local attackers to access image files with Bixby Vision privilege.

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


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

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

## Is CVE-2025-20970 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-20970 is a medium-severity missing authorization vulnerability in Samsung Mobile Bixby Vision, published on 7 May 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-20970 in the wild and no public exploit code.

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

## Sources

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

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