# CVE-2026-82933: Cleartext Transmission of Sensitive Information in mH-DEVELOPER

> Attackers on the same network can intercept cleartext HTTP traffic to steal credentials and hijack sessions on mH-DEVELOPER smart home modules.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/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-vrv2-qxr4-vjpx

## What is CVE-2026-82933?

CVE-2026-82933 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 sends its web interface and API traffic over unencrypted HTTP. Passwords, authentication tokens, and device commands are transmitted in cleartext. An attacker on the same network can intercept this traffic, steal credentials and tokens, and hijack sessions.

This issue was fixed in version 3.0.30

Weakness: CWE-1428 (Reliance on HTTP instead of HTTPS)

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


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

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

## Is CVE-2026-82933 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82933 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-82933 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-82933/ (Markdown: https://insights.sbomify.com/CVE-2026-82933/index.md)
```

## Sources

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

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