https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2025-56365.htmlhttps://patchthecve.com/cve/CVE-2025-56365.htmlTue, 13 Oct 2026 09:10:00 +0000MEDIUM 5.7: 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 chhttps://patchthecve.com/cve/CVE-2025-56364.htmlhttps://patchthecve.com/cve/CVE-2025-56364.htmlTue, 13 Oct 2026 09:10:00 +0000MEDIUM 5.7: A use of uninitialized value vulnerability exists in the Matter SDK (connectedhomeip) before 1.4.0, where the `GetDestinationGroupId().Value()` method is called without first checking whether a value exists. This leads to a crash when an InvokeCommand is sent without initializing the destination grohttps://patchthecve.com/cve/CVE-2025-56363.htmlhttps://patchthecve.com/cve/CVE-2025-56363.htmlTue, 13 Oct 2026 10:10:00 +0000MEDIUM 5.7: A null pointer dereference vulnerability exists in the Matter SDK (connectedhomeip) before 1.4.0, affecting the ReadRevisionAttribute function used in multiple clusters (Channel, Account Login, TargetNavigator, etc.). The function lacks proper validation of the delegate pointer before dereferencing.https://patchthecve.com/cve/CVE-2025-56362.htmlhttps://patchthecve.com/cve/CVE-2025-56362.htmlTue, 13 Oct 2026 10:10:00 +0000MEDIUM 5.7: A reachable assertion vulnerability exists in the Matter SDK (connectedhomeip) before 1.4.2, specifically within the Level Control cluster's periodic server tick logic. When a MoveToLevel command is sent and immediately followed by a write of OperationMode=2 (in the Pump Configuration and Control clhttps://patchthecve.com/cve/CVE-2025-56361.htmlhttps://patchthecve.com/cve/CVE-2025-56361.htmlTue, 13 Oct 2026 10:10:00 +0000MEDIUM 5.7: 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 Operation