# CVE-2026-82932: Missing Firewall Configuration in mH-DEVELOPER

> The smart home module fails to load firewall rules, exposing all services to the local network and allowing unauthorized access.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-grg4-hvg7-5g57

## What is CVE-2026-82932?

CVE-2026-82932 is a medium-severity vulnerability in F&F Filipowski mH-DEVELOPER, published on 28 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

mH-DEVELOPER smart home module does not load any firewall rules at startup. This leaves all listening services, including SSH, HTTP, WebSocket, and Node-RED, fully exposed on the LAN without access control. Any client on the same network can reach every service.

This issue was fixed in version 3.0.30

Weakness: CWE-923 (Improper Restriction of Communication Channel to Intended Endpoints)

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


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

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

## Is CVE-2026-82932 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82932 is a medium-severity vulnerability in F&F Filipowski mH-DEVELOPER, published on 28 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-82932 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-82932/ (Markdown: https://insights.sbomify.com/CVE-2026-82932/index.md)
```

## Sources

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

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