{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56361 exists.","fix":"No fix has been published for CVE-2025-56361 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56361 is a medium-severity denial of service vulnerability in n/a, published on 14 Jul 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-2025-56361 and fix it if it is affected.\n\nWhat it is: CVE-2025-56361 is a medium-severity denial of service vulnerability in n/a, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56361 exists.\n\nAffected product: n/a. 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-56361/ (Markdown: https://insights.sbomify.com/CVE-2025-56361/index.md)","id":"CVE-2025-56361","markdown":"https://insights.sbomify.com/CVE-2025-56361/index.md","name":"CVE-2025-56361","record":{"aliases":["GHSA-f6px-4w9c-rj4f"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Matter SDK","requires_auth":"low_privilege","summary":"Remote attackers can cause a denial of service in Matter devices by triggering an assertion failure in the Level Control cluster logic.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"matter","vendor":"csa-iot"}],"cvss":{"score":5.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"}],"description":"A reachable assertion vulnerability exists in the Matter SDK (connectedhomeip) 1.3 thru 1.4, specifically within the Level Control cluster's server tick logic (`emberAfLevelControlClusterServerTickCallback`). When a MoveToLevel command is executed and followed by a conflicting write to the OperationMode attribute (in the Pump Configuration and Control cluster), an invariant check (`minLevel \u003c currentLevel`) fails and causes the device to abort. This leads to a denial of service condition. The issue is confirmed in SDK versions 1.3 and 1.4 (commit ab3d5ae), and is triggered remotely without authentication.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Denial of service in n/a","id":"CVE-2025-56361","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2025-56362"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2025-56353"},"products":["n/a"],"published":"2026-07-14","related":[{"cvss_score":6.5,"headline":"Session establishment lock-up during replay of CASE Sigma1 messages","id":"CVE-2024-3297","kev_date_added":null,"published":"2024-07-24"},{"cvss_score":5.7,"headline":"Denial of service in n/a","id":"CVE-2025-56362","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":5.7,"headline":"Null dereference in n/a","id":"CVE-2025-56363","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":5.7,"headline":"Null dereference in n/a","id":"CVE-2025-56364","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":5.7,"headline":"Denial of service in n/a","id":"CVE-2025-56365","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":3.5,"headline":"In-Fabric Matter Cluster Attribute Disclosure","id":"CVE-2024-3454","kev_date_added":null,"published":"2024-07-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-05","vendors":["n/a"]},"summary":"Remote attackers can cause a denial of service in Matter devices by triggering an assertion failure in the Level Control cluster logic.","url":"https://insights.sbomify.com/CVE-2025-56361/"}