{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82928 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82928 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82928 is a high-severity vulnerability in F\u0026F 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."},"fix_prompt":"Check this codebase for CVE-2026-82928 and fix it if it is affected.\n\nWhat it is: CVE-2026-82928 is a high-severity vulnerability in F\u0026F 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.\nExploitation: There is no known exploitation of CVE-2026-82928 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-82928/ (Markdown: https://insights.sbomify.com/CVE-2026-82928/index.md)","id":"CVE-2026-82928","markdown":"https://insights.sbomify.com/CVE-2026-82928/index.md","name":"CVE-2026-82928","record":{"aliases":["GHSA-27f6-7954-3wm7"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"smart home module","requires_auth":"none","summary":"Hardcoded SSH key allows attackers to gain root access on mH-DEVELOPER smart home devices, leading to full system compromise.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1242","name":"Inclusion of Undocumented Features or Chicken Bits"}],"description":"mH-DEVELOPER smart home module contains a hardcoded SSH public key in /root/.ssh/authorized_keys, serving as a potential backdoor. The SSH daemon allows root login via key authentication and starts automatically. An attacker with the matching private key can gain a root shell on any affected device, resulting in full system compromise. The key cannot be removed without remounting the file system and survives a factory reset. Vendor notes that this functionality was used only for service purposes.\n\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":"Undocumented access path in mH-DEVELOPER","id":"CVE-2026-82928","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":"Use of Shared Cryptographic Key in mH-DEVELOPER","id":"CVE-2026-82929"},"packages":[],"prev":{"headline":"Null dereference in mTower","id":"CVE-2026-82927"},"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":"total"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["F\u0026F Filipowski"]},"summary":"Hardcoded SSH key allows attackers to gain root access on mH-DEVELOPER smart home devices, leading to full system compromise.","url":"https://insights.sbomify.com/CVE-2026-82928/"}