# CVE-2025-10971: Insecure Storage of Sensitive Information

> Attackers can retrieve embedded sensitive data from the MeetMe mobile application, exposing confidential information to unauthorized users.

- **Severity:** High 8.8 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L`)
- **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:** 2 Dec 2025
- **Updated:** 2 Dec 2025
- **Also known as:** GHSA-x85p-x37v-q546

## What is CVE-2025-10971?

CVE-2025-10971 is a high-severity vulnerability in FERMAX ELECTRÓNICA S.A.U MeetMe, published on 2 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insecure Storage of Sensitive Information vulnerability in MeetMe on iOS, Android allows Retrieve Embedded Sensitive Data. This issue affects MeetMe: through v2.2.5.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

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


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

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

## Is CVE-2025-10971 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10971 is a high-severity vulnerability in FERMAX ELECTRÓNICA S.A.U MeetMe, published on 2 Dec 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-10971 in the wild and no public exploit code.

Affected product: FERMAX ELECTRÓNICA S.A.U MeetMe. 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-10971/ (Markdown: https://insights.sbomify.com/CVE-2025-10971/index.md)
```

## Sources

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

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