# CVE-2025-14817: Factory Mode App Exists Privilege Escalation Issue Allowing Third-Party Apps to Open ADB

> Third-party apps can bypass permissions to enable ADB debugging on Tecno devices, allowing unauthorized access and potential privilege escalation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Dec 2025
- **Updated:** 17 Dec 2025
- **Also known as:** GHSA-q4hg-gxj2-4c9q

## What is CVE-2025-14817?

CVE-2025-14817 is a medium-severity missing authorization vulnerability in Tecno Pova6 Pro 5G, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The component com.transsion.tranfacmode.entrance.main.MainActivity in com.transsion.tranfacmode has no permission control and can be accessed by third-party apps which can construct intents to directly open adb debugging functionality without user interaction.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Transsion Hios.

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

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

## Is CVE-2025-14817 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14817 is a medium-severity missing authorization vulnerability in Tecno Pova6 Pro 5G, published on 17 Dec 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-14817 in the wild and no public exploit code.

Affected product: Tecno Pova6 Pro 5G. 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-14817/ (Markdown: https://insights.sbomify.com/CVE-2025-14817/index.md)
```

## Sources

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

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