# CVE-2026-82929: Use of Shared Cryptographic Key in mH-DEVELOPER

> Attackers can intercept credentials and traffic via man-in-the-middle attacks due to shared hard-coded SSH keys in mH-DEVELOPER smart home modules.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-mh6x-hrvc-rqhh

## What is CVE-2026-82929?

CVE-2026-82929 is a medium-severity vulnerability in F&F Filipowski mH-DEVELOPER, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mH-DEVELOPER smart home module uses the same hard-coded SSH host keys on every device, with no per-device key generation. An attacker who extracts these keys from the firmware can set up a rogue SSH server that clients will trust without warning, enabling man-in-the-middle attacks and credential interception.
This issue was fixed in version 3.0.30

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

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


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

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

## Is CVE-2026-82929 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82929 is a medium-severity vulnerability in F&F Filipowski mH-DEVELOPER, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82929 in the wild and no public exploit code.

Affected product: F&F Filipowski mH-DEVELOPER. 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-82929/ (Markdown: https://insights.sbomify.com/CVE-2026-82929/index.md)
```

## Sources

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

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