# CVE-2025-56019: Auth bypass in n/a

> Unauthorized mobile apps can connect via Bluetooth without authentication, blocking legitimate users and causing denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 2 Oct 2025
- **Updated:** 2 Oct 2025
- **Also known as:** GHSA-hvhc-p67p-jh2h

## What is CVE-2025-56019?

CVE-2025-56019 is a medium-severity authentication bypass vulnerability in n/a, published on 2 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An insecure permission vulnerability exists in the Agasta Easytouch+ version 9.3.97 The device allows unauthorized mobile applications to connect via Bluetooth Low Energy (BLE) without authentication. Once an unauthorized connection is established, legitimate applications are unable to connect, causing a denial of service. The attack requires proximity to the device, making it exploitable from an adjacent network location.

Weakness: CWE-277 (Insecure Inherited Permissions)

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

It affects 1 product.


Products: Agasta Easy Touch Plus Firmware.

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

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

## Is CVE-2025-56019 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56019 exists.

Public exploit code:

- This report is for CVE-2025-56019 reserved for Easytouch+product for BLE authentication vulnerability assigned to Discoverer Yashodhan Vivek Mandke. Please download the report pdf in this repositoy (github_poc): https://github.com/Yashodhanvivek/Agatsa-EasyTouch-Plus---CVE-2025-56019

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56019 is a medium-severity authentication bypass vulnerability in n/a, published on 2 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56019 exists.

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

## Sources

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

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