Medium

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

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

Published Sep 28, 2026 · Updated Oct 16, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: CERT-PL

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

F&F Filipowski

mH-DEVELOPER

CVSS base

6.3

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (F&F Filipowski mH-DEVELOPER).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
F&F Filipowski	mH-DEVELOPER	< 3.0.30	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Attack requirements

Present

Privileges required

None

User interaction

None

Scope

Confidentiality (vulnerable system)

Low

Integrity (vulnerable system)

Low

Availability (vulnerable system)

None

Confidentiality (subsequent)

None

Integrity (subsequent)

None

Availability (subsequent)

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
6.3	CVSS 4.0	Medium	—	—	cvd@cert.pl via NIST National Vulnerability Database
6.3	CVSS 4.0	Medium	—	—	CERT-PL via CVE Program (cve.org) e CISA ADP

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

(score shown at the top: cvd@cert.pl)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-321

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Affected products added · f&f filipowski/mh-developer
Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 6.3
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Deferred
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 28, 2026 · CERT-PL

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

2 on the record

www.fif.com.pl/pl/strona-glowna/1367-mh-developer.html
product, NIST National Vulnerability Database
cert.pl/posts/2026/09/CVE-2026-82928/
third-party-advisory, NIST National Vulnerability Database

Elsewhere on this site

F&F Filipowski
every CVE for this vendor

CWE-321
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-82936 Denial of Service in mH-DEVELOPER 17d
High CVE-2026-82928 Undocumented access path in mH-DEVELOPER 17d
Medium CVE-2026-82930 Missing Authentication in mH-DEVELOPER 17d
Medium CVE-2026-82932 Missing Firewall Configuration in mH-DEVELOPER 17d
Medium CVE-2026-82933 Cleartext Transmission of Sensitive Information in mH-DEVELOPER 17d
Medium CVE-2026-82935 Use of End-of-Life components in mH-DEVELOPER 17d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-82929 is "Use of Shared Cryptographic Key in mH-DEVELOPER", rated Medium. It affects mH-DEVELOPER (F&F Filipowski); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.