dbcve.org
MatterApplication · Csa Iot

CVE-2025-56361

HIGH · 7.5 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A reachable assertion in Matter SDK's Level Control cluster server tick callback fails when a MoveToLevel command is followed by a conflicting write to the OperationMode attribute in the Pump Configuration cluster, causing an invariant check (minLevel < currentLevel) to abort the device.

MitigationFix the invariant check in emberAfLevelControlClusterServerTickCallback to handle conflicting OperationMode writes gracefully, or add validation before the assertion to prevent the abort condition.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MatterApplication
Affected:= 1.3.0.0= 1.4.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Csa IoT Matter SDK version
    Inspect the SDK version file or library metadata (e.g., check your package.json, SDK release notes, or embedded version string in the matter library binary)
    Affected if Version is exactly 1.3.0.0 or exactly 1.4.0.0
  2. Verify Level Control cluster server is in use
    Examine your Matter device configuration or cluster definition files to confirm the Level Control cluster server (cluster ID 0x0008) is enabled in the endpoint(s)
    Affected if Level Control cluster server is enabled and responding to commands
  3. Confirm Pump Configuration cluster is deployed
    Review your Matter device's cluster configuration to determine if the Pump Configuration and Control cluster (cluster ID 0x0204) is present on any endpoint
    Affected if Pump Configuration cluster with OperationMode attribute (attribute ID 0x0005) is present in the device data model
  4. Check for MoveToLevel and OperationMode write interaction
    Review application logs or network traces for incoming MoveToLevel commands (0x0000 command ID under Level Control cluster) followed by WriteAttribute requests targeting the OperationMode attribute in the Pump Configuration cluster
    Affected if Both operations occur in sequence within the same transaction window, triggering the invariant check failure

A device is affected if it runs Csa IoT Matter version 1.3.0.0 or 1.4.0.0 and has both the Level Control cluster server and Pump Configuration cluster with OperationMode attribute enabled, where a MoveToLevel command can be followed by a conflicting OperationMode write.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix the invariant check in emberAfLevelControlClusterServerTickCallback to handle conflicting OperationMode writes gracefully, or add validation before the assertion to prevent the abort condition.

Fix this in Matter Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-56361 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-56361 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data