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

> Attackers can inject arbitrary keystrokes via spoofed Bluetooth HID devices on JXL Car Android Players, potentially leading to unauthorized control.

- **Severity:** High 7.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A: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:** 4 Dec 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-hwhh-rpxf-fpxm

## What is CVE-2025-63896?

CVE-2025-63896 is a high-severity missing authorization vulnerability in n/a, published on 4 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in the Bluetooth Human Interface Device (HID) of JXL 9 Inch Car Android Double Din Player Android v12.0 allows attackers to inject arbitrary keystrokes via a spoofed Bluetooth HID device.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Jxlindia Jxl 9 Inch Car Android Double Din Player Firmware.

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

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

## Is CVE-2025-63896 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63895](https://insights.sbomify.com/CVE-2025-63895/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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