# CVE-2025-25370: Information disclosure in n/a

> A physically proximate attacker can obtain sensitive information from realme GT 2 devices via the show app only setting function.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 14 May 2025
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-m7cj-8qx5-j738

## What is CVE-2025-25370?

CVE-2025-25370 is a medium-severity vulnerability in n/a, published on 14 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in realme GT 2 (RMX3311) running Android 14 with realme UI 5.0 allows a physically proximate attacker to obtain sensitive information via the show app only setting function.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-25370 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25370 is a medium-severity vulnerability in n/a, published on 14 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-25370 in the wild and no public exploit code.

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

## Sources

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

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