{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-56558 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-56558 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56558 is a low-severity vulnerability in Dyson MQTT server, published on 29 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-56558 and fix it if it is affected.\n\nWhat it is: CVE-2025-56558 is a low-severity vulnerability in Dyson MQTT server, published on 29 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-56558 in the wild and no public exploit code.\n\nAffected product: Dyson MQTT server. 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-2025-56558/ (Markdown: https://insights.sbomify.com/CVE-2025-56558/index.md)","id":"CVE-2025-56558","markdown":"https://insights.sbomify.com/CVE-2025-56558/index.md","name":"CVE-2025-56558","record":{"aliases":["GHSA-h2c5-5pm8-g4x6"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Dyson IoT device","requires_auth":"high_privilege","summary":"An attacker can control a removed Dyson device via MQTT if they possess valid AWS credentials and the device serial number, bypassing ownership checks.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-420","name":"Unprotected Alternate Channel"}],"description":"The Dyson MQTT server (2022 and possibly later) allows publications and subscriptions by a client that has the correct values of AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, and device serial number, even if a device (such as a Pure Hot+Cool device) has been removed and is not visible in the supported MyDyson app. This could allow an unexpected actor to obtain control and set the room temperature (up to 37 Celsius) if ownership of the device is transferred without wiping the device. NOTE: the Supplier's position is that this is a potential vulnerability that dates back 4 years ago in 2022 and \"we are unable to replicate that anymore.\" Based on the submitted report, in order to leverage this issue, an attacker needs to own a Dyson device with full privileges, sniff for the AWS credentials, and then transfer ownership of that Dyson device to the victim. Even if these steps were successfully accomplished, the attacker only acquires the ability to configure the Dyson device within its safe operating range, and does not acquire the ability to execute code on the device or obtain sensitive information.","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":"Business logic in MQTT server","id":"CVE-2025-56558","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2025-56562"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-56557"},"products":["MQTT server"],"published":"2025-10-29","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-01-13","vendors":["Dyson"]},"summary":"An attacker can control a removed Dyson device via MQTT if they possess valid AWS credentials and the device serial number, bypassing ownership checks.","url":"https://insights.sbomify.com/CVE-2025-56558/"}