CVE-2026-82936: Denial of Service in mH-DEVELOPER

Published Sep 28, 2026
·
Updated

mH-DEVELOPER smart home module is vulnerable to Denial of Service due to uncontrolled resource consumption. The Express bodyParser is configured with a 250 MB limit for JSON and URL-encoded request bodies. An authenticated attacker on the LAN can send large request bodies that exhausts buffers in RAM, causing out-of-memory conditions and crashing the fh-node process, resulting in denial of service. The successful attack depends on the current memory usage of the device which is not under full control of the attacker. Critically, due to CVE-2026-82930 all endpoints can be queried unauthenticated, so any user on LAN can perform this attack.

This issue was fixed in version 3.0.30

Affected Software

1 affected component
mH-DEVELOPER mH-DEVELOPER smart home module<3.0.30

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade mH-DEVELOPER to a version that resolves this vulnerability.

    Fixed in 3.0.30

Event History

Sep 28, 2026
CVE Published
via MITRE·12:12 PM
Data Sourced
via MITRE·12:12 PM
DescriptionWeakness
Data Sourced
via NVD·01:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue in practice?

Any user on the local network can perform the attack because CVE-2026-82930 allows endpoints to be queried without authentication. The issue is therefore not limited to authenticated users in affected deployments.

2

What conditions affect whether an attack succeeds?

An attacker can submit large JSON or URL-encoded request bodies, up to the configured 250 MB limit, to consume RAM and crash the fh-node process. Success depends on the device's current memory usage, which the attacker does not fully control.

3

Are default request-size settings affected?

The affected configuration uses Express bodyParser with a 250 MB limit for both JSON and URL-encoded bodies. This limit permits request sizes large enough to exhaust available RAM under suitable memory conditions.

4

What version fixes the issue?

The issue was fixed in version 3.0.30.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203