Use of Shared Cryptographic Key in mH-DEVELOPER

Answer in brief

CVE-2026-82929 records a Medium severity (CVSS 6.3) vulnerability in Use of Shared Cryptographic Key in mH-DEVELOPER. The current sources do not mark it as known exploited. The current feed maps F&F Filipowski/mH-DEVELOPER (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 28, 2026Updated Sep 28, 2026Source checked Sep 28, 2026First seen by HOL Sep 28, 2026Material review Sep 28, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps F&F Filipowski/mH-DEVELOPER (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
F&F Filipowski/mH-DEVELOPERgeneric	>=0 <3.0.30	3.0.30

Recommended response

Check inventory. Check lockfiles and deployed manifests for F&F Filipowski/mH-DEVELOPER.
Review the reported fix. Update F&F Filipowski/mH-DEVELOPER to 3.0.30 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 28, 2026

Sources and claim methodology

Upstream source 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

Quoted source text, attributed separately from HOL analysis.