# CVE-2025-27389: Application Installation Source Verification Flaw May Lead to Risk Detection Bypass

> Attackers can bypass risk detection to install malicious applications on ColorOS devices without triggering security warnings.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA: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:** 5 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-gm7c-g54p-mxf6

## What is CVE-2025-27389?

CVE-2025-27389 is a medium-severity vulnerability in ColorOS, published on 5 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw exists in the verification of application installation sources within ColorOS. Under specific conditions, this issue may cause the risk detection mechanism to fail, which could allow malicious applications to be installed without proper warning.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2025-27389 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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