Security Resilience

CVE-2025-56364

Csa-Iot Matter ≤ 1.4.0.0

Published
14 July 2026
Modified
13 October 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0020 9th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-56364 is a medium-severity Use of Uninitialized Variable (CWE-457) vulnerability in Csa-Iot Matter. Its CVSS base score is 5.7 (Medium).

Operationally, ranked at the 9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

destination group ID. The issue affects all versions before commit 0360cc3 (Dec 5, 2024) and leads to denial of service through SIGABRT. It is fixed by adding a .HasValue() check before access.

CWE(s)
CWE-457

Related Threats

CVEs Like This One

CVE-2025-56365Same product: Csa-Iot Matter
CVE-2025-56361Same product: Csa-Iot Matter
CVE-2025-56362Same product: Csa-Iot Matter
CVE-2024-3454Same product: Csa-Iot Matter
CVE-2025-56363Same product: Csa-Iot Matter
CVE-2024-3297Same product: Csa-Iot Matter
CVE-2026-17968Shared CWE-457
CVE-2025-2014Shared CWE-457
CVE-2026-11039Shared CWE-457
CVE-2025-2024Shared CWE-457

Affected Assets

csa-iot
matter
≤ 1.4.0.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and static analysis directly find uses of uninitialized variables before deployment.

SA-15 Development Process, Standards, and Tools partial match

Documented development standards and tools can enforce initialization requirements in code.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can mandate explicit variable initialization to avoid uninitialized use.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly catch uninitialized-variable defects via static analysis and code review while the control encompasses many additional development controls.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect uninitialized-variable bugs, but the control is broader.

A.8.28 Secure coding partial match
prevents

Secure coding explicitly requires variable initialization and static-analysis checks.

References