# CVE-2025-50861: Missing authorization in n/a

> An exported activity in the Lotus Cars Android app allows unauthenticated access, potentially causing denial of service or logic abuse.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-cgr9-p7j2-h64m

## What is CVE-2025-50861?

CVE-2025-50861 is a medium-severity missing authorization vulnerability in n/a, published on 14 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Lotus Cars Android app (com.lotus.carsdomestic.intl) 1.2.8 contains an exported component, PushDeepLinkActivity, which is accessible without authentication via ADB or malicious apps. This poses a risk of unintended access to application internals and can cause denial of service or logic abuse.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-50861 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50861 is a medium-severity missing authorization vulnerability in n/a, published on 14 Aug 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-50861 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-50861/ (Markdown: https://insights.sbomify.com/CVE-2025-50861/index.md)
```

## Sources

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

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