# CVE-2025-2766: 70mai A510 Use of Default Password Authentication Bypass Vulnerability

> Network-adjacent attackers can bypass authentication using default credentials to execute arbitrary code as root on 70mai A510 dashcams.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 6 Jun 2025
- **Updated:** 9 Jun 2025
- **Also known as:** GHSA-7478-8pwj-vcwr

## What is CVE-2025-2766?

CVE-2025-2766 is a high-severity vulnerability in 70mai A510, published on 6 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

70mai A510 Use of Default Password Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of 70mai A510. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the default configuration of user accounts. The configuration contains default password. An attacker can leverage this vulnerability to bypass authentication and execute arbitrary code in the context of the root. Was ZDI-CAN-24996.

Weakness: CWE-1393 (Use of Default Password)

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

It affects 1 product.


Products: 70mai A510 Firmware.

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

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

## Is CVE-2025-2766 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2766 is a high-severity vulnerability in 70mai A510, published on 6 Jun 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-2766 in the wild and no public exploit code.

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

## Sources

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

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