{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82936 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82936 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82936 is a medium-severity denial of service 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-82936 and fix it if it is affected.\n\nWhat it is: CVE-2026-82936 is a medium-severity denial of service 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-82936 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-82936/ (Markdown: https://insights.sbomify.com/CVE-2026-82936/index.md)","id":"CVE-2026-82936","markdown":"https://insights.sbomify.com/CVE-2026-82936/index.md","name":"CVE-2026-82936","record":{"aliases":["GHSA-289h-w85v-v5r6"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"smart home module","requires_auth":"low_privilege","summary":"An attacker on the local network can crash the smart home module by sending large request bodies, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"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.\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":"Denial of Service in mH-DEVELOPER","id":"CVE-2026-82936","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Apache bRPC: Race Condition on the Shared Socket Input Buffer in the RDMA Transport Causes Remote Denial of Service","id":"CVE-2026-82942"},"packages":[],"prev":{"headline":"Use of End-of-Life components in mH-DEVELOPER","id":"CVE-2026-82935"},"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":"An attacker on the local network can crash the smart home module by sending large request bodies, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-82936/"}