{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56365 exists.","fix":"No fix has been published for CVE-2025-56365 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56365 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-56365 and fix it if it is affected.\n\nWhat it is: CVE-2025-56365 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-56365 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-56365/ (Markdown: https://insights.sbomify.com/CVE-2025-56365/index.md)","id":"CVE-2025-56365","markdown":"https://insights.sbomify.com/CVE-2025-56365/index.md","name":"CVE-2025-56365","record":{"aliases":["GHSA-wj9x-8hv5-2p36"],"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":"An attacker can crash Matter SDK devices by sending commands to nonexistent endpoints, causing a denial of service.","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) before 1.4.0, in the interaction model command processing logic. When an InvokeCommandRequest is sent to a nonexistent endpoint and cluster (e.g., 0x34), the code incorrectly treats the endpoint as valid due to missing checks in CodegenDataModelProvider::Invoke. This causes a VerifyOrDie failure in ProcessCommandDataIB and results in a crash (SIGABRT). The issue has been acknowledged and fixed in a later revision (PR #37207).","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-56365","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-56379"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2025-56364"},"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-56361","kev_date_added":null,"published":"2026-07-14"},{"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":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":"An attacker can crash Matter SDK devices by sending commands to nonexistent endpoints, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2025-56365/"}