dbcve.org
MatterApplication · Csa Iot

CVE-2025-56363

HIGH · 7.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 1.4.0.0 or later.
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 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. A remote unauthenticated attacker can exploit this issue by sending a crafted read request, causing the device to crash (denial of service). This issue has been confirmed in SDK version v1.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 null pointer dereference vulnerability exists in the Matter SDK (connectedhomeip) before version 1.4.0 in the ReadRevisionAttribute function. The function fails to validate the delegate pointer before dereferencing it, allowing a remote unauthenticated attacker to crash the device by sending a crafted read request. This affects multiple clusters including Channel, Account Login, and TargetNavigator.

MitigationUpgrade the Matter SDK to version 1.4.0 or later, which contains the proper delegate pointer validation. If upgrading is not immediately feasible, implement input validation checks in affected clusters before calling ReadRevisionAttribute.

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.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 Matter SDK version
    Locate the connectedhomeip or Matter SDK version in your project dependencies, build files, or firmware BOM. This is typically found in a manifest, package.json, or build configuration file.
    Affected if The installed version is earlier than 1.4.0.0 (or the SDK version is unknown and cannot be determined) and the product implements Matter functionality.
  2. Verify presence of affected clusters
    Review your application's cluster implementation or configuration to determine if any of these clusters are enabled: Channel cluster, Account Login cluster, or TargetNavigator cluster. Check cluster implementation files or cluster lists in your device configuration.
    Affected if Any of the Channel, Account Login, or TargetNavigator clusters are implemented or enabled in your Matter device.
  3. Check ReadRevisionAttribute usage
    Search your codebase for calls to the ReadRevisionAttribute function within cluster handlers. This function handles revision attribute reads for cluster implementations.
    Affected if The ReadRevisionAttribute function is present in your codebase and is called by cluster handlers for the affected clusters.
  4. Inspect delegate pointer handling
    Review the ReadRevisionAttribute function source code in your SDK version to verify if delegate pointer validation (null check) occurs before the pointer is dereferenced.
    Affected if The function lacks proper null pointer validation on the delegate before dereferencing it.

Your environment is affected if you use a Matter SDK version earlier than 1.4.0.0, have any of the Channel, Account Login, or TargetNavigator clusters enabled, and the ReadRevisionAttribute function is called without prior delegate pointer validation.

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
Upgrade available Upgrade to 1.4.0.0 or later
Fixed in 1.4.0.0
Interim mitigation

Upgrade the Matter SDK to version 1.4.0 or later, which contains the proper delegate pointer validation. If upgrading is not immediately feasible, implement input validation checks in affected clusters before calling ReadRevisionAttribute.

Recommended fix High confidence

Matter SDK 1.4.0.0 or later

  1. Upgrade the Matter SDK (connectedhomeip) to version 1.4.0.0 or later
  2. Rebuild and redeploy any applications or devices using the Matter SDK
  3. Verify that the ReadRevisionAttribute function now properly validates the delegate pointer before dereferencing
  4. Test that devices no longer crash when receiving crafted read requests to affected clusters (Channel, Account Login, TargetNavigator, etc.)

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

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 the upgrade done

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-56363 — 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-56363 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