# CVE-2025-20701: Auth bypass in AB156x, AB157x, AB158x, AB159x series

> Attackers can pair Bluetooth audio devices without consent, leading to remote privilege escalation in Airoha Bluetooth audio SDKs.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 4 Aug 2025
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-jf8q-5hx8-3j27

## What is CVE-2025-20701?

CVE-2025-20701 is a high-severity authentication bypass vulnerability in Airoha Technology Corp. AB156x, AB157x, AB158x, AB159x series, published on 4 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Airoha Bluetooth audio SDK, there is a possible way to pair Bluetooth audio device without user consent. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2025-20701 being exploited?

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

Public exploit code:

- Unauthorized Bluetooth Classic pairing behavior consistent with CVE-2025-20701 on Skullcandy Dime 3 earbuds. (github_poc): https://github.com/x0jac0b0x/skullcandy-dime3-cve-2025-20701

## Fix prompt for AI coding agents

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

What it is: CVE-2025-20701 is a high-severity authentication bypass vulnerability in Airoha Technology Corp. AB156x, AB157x, AB158x, AB159x series, published on 4 Aug 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-20701 in the wild and no public exploit code.

Affected product: Airoha Technology Corp. AB156x, AB157x, AB158x, AB159x series. 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-20701/ (Markdown: https://insights.sbomify.com/CVE-2025-20701/index.md)
```

## Sources

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

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