dbcve.org
MatterApplication · Csa Iot

CVE-2025-56362

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) 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 cluster), the server tick function violates the assertion `currentLevel < maxLevel`, resulting in a crash. This can be exploited remotely without authentication to cause denial of service. Affected versions include 1.3 and 1.4 (commit ab3d5ae).

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 · high confidence

A reachable assertion vulnerability exists in the Matter SDK (connectedhomeip) before version 1.4.2 in the Level Control cluster's periodic server tick logic. When a MoveToLevel command is immediately followed by a write of OperationMode=2 in the Pump Configuration and Control cluster, the server tick function violates the assertion `currentLevel < maxLevel`, causing a crash. This can be exploited remotely without authentication to cause denial of service.

MitigationUpgrade Matter SDK (connectedhomeip) to version 1.4.2 or later. Review implementations using the Level Control and Pump Configuration clusters to ensure the specific command sequence cannot be triggered or is handled safely.

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 the Matter SDK version
    Locate the connectedhomeip or Matter SDK library in your firmware or application (check package.json, firmware metadata, or library version file). Compare it against the affected versions (1.3.0.0, 1.4.0.0) and the fixed version (1.4.2).
    Affected if The installed version is 1.3.0.0 or 1.4.0.0 (any version before 1.4.2).
  2. Verify Level Control cluster is implemented
    Check if your Matter device or application implements the Level Control cluster (cluster ID 0x0008). This is typically found in the device's data model, cluster list, or cluster implementation files.
    Affected if The Level Control cluster is present in your implementation.
  3. Verify Pump Configuration and Control cluster is implemented
    Check if your Matter device or application implements the Pump Configuration and Control cluster (cluster ID 0x0200). Look in the cluster list, data model, or cluster implementation files.
    Affected if The Pump Configuration and Control cluster is present in your implementation.
  4. Determine exposure of clusters to network
    Check if the Level Control and Pump Configuration clusters are exposed to network or remote access (not limited to local commissioning only). Review your access control configuration and network exposure settings.
    Affected if Both clusters are network-accessible and can receive commands remotely without authentication.

You are affected if your Matter SDK version is before 1.4.2 AND your implementation includes both the Level Control cluster and the Pump Configuration and Control cluster with network exposure.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Matter SDK (connectedhomeip) to version 1.4.2 or later. Review implementations using the Level Control and Pump Configuration clusters to ensure the specific command sequence cannot be triggered or is handled safely.

Recommended fix High confidence

Matter SDK version 1.4.2 or latest stable release

  1. Identify the current Matter SDK (connectedhomeip) version in use - check for versions 1.3.0.0 or 1.4.0.0
  2. Upgrade the Matter SDK to version 1.4.2 or later (the official description states the vulnerability exists 'before 1.4.2')
  3. After upgrading, rebuild the Matter SDK and any applications that depend on it
  4. Redeploy the updated Matter SDK to all affected devices and controllers
  5. Verify the Level Control cluster and Pump Configuration and Control cluster functionality works correctly after the update
Caveat Review release notes for 1.4.2 for any breaking changes in Level Control or Pump Configuration clusters; test existing device firmware and controller integrations thoroughly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Matter Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-56362 — 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-56362 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