CVE-2025-56361 matter vulnerability
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 < 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.
Quick answer
csa-iot matter should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- 1.3.0.0
- 1.4.0.0
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2025-56361 affects csa-iot matter and is rated high. 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`). Fix this first on exposed systems, shared workstations, and file-processing workflows. The practical fix is to upgrade Matter SDK connectedhomeip to the latest vendor-supported release that includes the Level Control crash fix, then verify the risky path is closed.
- Inventory every server, app, package, desktop, device, container, or workflow that uses csa-iot matter.
- Check the installed version and configuration against CVE-2025-56361 and the linked advisory.
- Apply the vendor fix: upgrade Matter SDK connectedhomeip to the latest vendor-supported release that includes the Level Control crash fix.
- Limit untrusted Matter device traffic and test command handling in a safe lab before restoring exposure.
- Disable or isolate the affected feature if you cannot update right away.
- Review device crash logs, restart spikes, and unusual Matter command traffic.
- Rotate secrets, rebuild affected systems, or reset sessions if you suspect compromise.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm csa-iot matter is running the patched version or the approved mitigation is active.
- Confirm affected public, admin, desktop, media, model, or device access is limited to trusted users.
- Repeat a safe test of the risky workflow and confirm the issue no longer appears.
- Review logs after the fix for crashes, bypass attempts, file access, process launches, or suspicious changes.
- Save version, config, log, and scan evidence for your remediation record.
Related categories
Trusted references
FAQ
What is affected by CVE-2025-56361?
csa-iot matter versions listed as affected should be reviewed: 1.3.0.0, 1.4.0.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.