# CVE-2026-75558: Botslab G980H Dashcams Use of Hard-coded Cryptographic Key

> Attackers can extract hard-coded keys from Botslab G980H dashcam firmware to decrypt WiFi credentials and access the device network.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 24 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-26fw-w27q-phjj

## What is CVE-2026-75558?

CVE-2026-75558 is a medium-severity vulnerability in Botslab G980H, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Botslab G980H dash camera firmware uses a hard-coded cryptographic key and initialization vector to protect WiFi credentials communicated by the device. An attacker who obtains the protected credential and extracts the cryptographic material from the firmware could recover the WiFi password and gain unauthorized access to the device network.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2026-75558?


## How do I fix CVE-2026-75558?

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

## Is CVE-2026-75558 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75558 and fix it if it is affected.

What it is: CVE-2026-75558 is a medium-severity vulnerability in Botslab G980H, published on 24 Sep 2026. 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-2026-75558 in the wild and no public exploit code.

Affected product: Botslab G980H. 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-2026-75558/ (Markdown: https://insights.sbomify.com/CVE-2026-75558/index.md)
```

## Sources

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

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