# CVE-2025-2190: Other in com.transsnet.store

> A man-in-the-middle vulnerability in the TECNO mobile app allows attackers to inject code, posing a significant security risk to users.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2025
- **Updated:** 9 Sep 2025
- **Also known as:** GHSA-xp2h-p87p-622p

## What is CVE-2025-2190?

CVE-2025-2190 is a high-severity vulnerability in TECNO com.transsnet.store, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The mobile application (com.transsnet.store) has a man-in-the-middle attack vulnerability, which may lead to code injection risks.

Weakness: CWE-297 (Improper Validation of Certificate with Host Mismatch)

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

It affects 1 product.


Products: Tecno Com.transsnet.store.

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

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

## Is CVE-2025-2190 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2190 is a high-severity vulnerability in TECNO com.transsnet.store, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2190 in the wild and no public exploit code.

Affected product: TECNO com.transsnet.store. 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-2190/ (Markdown: https://insights.sbomify.com/CVE-2025-2190/index.md)
```

## Sources

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

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