{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82929 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82929 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82929 is a medium-severity vulnerability in F\u0026F Filipowski mH-DEVELOPER, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-82929 and fix it if it is affected.\n\nWhat it is: CVE-2026-82929 is a medium-severity vulnerability in F\u0026F Filipowski mH-DEVELOPER, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-82929 in the wild and no public exploit code.\n\nAffected product: F\u0026F Filipowski mH-DEVELOPER. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-82929/ (Markdown: https://insights.sbomify.com/CVE-2026-82929/index.md)","id":"CVE-2026-82929","markdown":"https://insights.sbomify.com/CVE-2026-82929/index.md","name":"CVE-2026-82929","record":{"aliases":["GHSA-mh6x-hrvc-rqhh"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"smart home module","requires_auth":"none","summary":"Attackers can intercept credentials and traffic via man-in-the-middle attacks due to shared hard-coded SSH keys in mH-DEVELOPER smart home modules.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"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.\nThis issue was fixed in version 3.0.30","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Use of Shared Cryptographic Key in mH-DEVELOPER","id":"CVE-2026-82929","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Missing Authentication in mH-DEVELOPER","id":"CVE-2026-82930"},"packages":[],"prev":{"headline":"Undocumented access path in mH-DEVELOPER","id":"CVE-2026-82928"},"products":["mH-DEVELOPER"],"published":"2026-09-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["F\u0026F Filipowski"]},"summary":"Attackers can intercept credentials and traffic via man-in-the-middle attacks due to shared hard-coded SSH keys in mH-DEVELOPER smart home modules.","url":"https://insights.sbomify.com/CVE-2026-82929/"}