Security readout for executives and security teams
Plain-English summary
This flaw can remotely crash affected Matter devices built with connectedhomeip 1.3 through 1.4. It does not indicate data theft or device takeover, but it can interrupt availability of smart-home or IoT functions. Public sources do not identify specific downstream vendors or patched firmware releases.
Executive priority
Treat this as a high-priority availability risk for Matter-based device fleets, especially where device downtime affects operations or customer trust. The immediate task is exposure discovery because public sources do not identify specific downstream products or available patches.
Technical view
A reachable assertion in the Level Control cluster server tick path can fail after a MoveToLevel command and conflicting OperationMode write in the Pump Configuration and Control cluster. The failed invariant aborts the device, causing denial of service. Sources state SDK 1.3 and 1.4, including commit ab3d5ae, are affected.
Likely exposure
Exposure is most likely in products or firmware that embed Matter SDK connectedhomeip versions 1.3 or 1.4. The CVE data does not name specific affected device vendors, models, CPEs, or cloud services, so asset mapping requires SBOMs, firmware notes, or vendor confirmation.
Exploitation context
The provided CVSS vector indicates network access, low complexity, no privileges, and no user interaction. The source bundle says remote unauthenticated triggering is possible. It is not in KEV, and no cited source in the bundle states active exploitation in the wild.
Researcher notes
Evidence supports a reachable assertion denial of service in connectedhomeip, but downstream impact is under-specified. Avoid assuming every Matter device is affected. Focus research on firmware provenance, cluster support, SDK version lineage, and whether vendors have backported a fix without changing public version labels.
Mitigation direction
- Inventory Matter-enabled products and firmware using connectedhomeip 1.3 or 1.4.
- Check project-chip issue 38619 and vendor advisories for official fixes or workarounds.
- Prioritize firmware updates once vendors publish corrected builds.
- Restrict untrusted network access to Matter device control paths where operationally feasible.
- Ask suppliers for SBOM or written confirmation of connectedhomeip version exposure.
Validation and detection
- Review SBOMs, build manifests, or firmware release notes for connectedhomeip 1.3 or 1.4.
- Confirm whether the device implements the relevant Level Control and Pump Configuration clusters.
- Track vendor advisories for model-specific impact, fix availability, and deployment instructions.
- Perform any crash reproduction only in an isolated lab using vendor-approved guidance.
- Verify updated firmware no longer references the affected SDK version or vulnerable commit.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-617: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-56361 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/project-chip/connectedhomeip/issues/38619CVE reference, mitre
- https://github.com/project-chip/connectedhomeip/CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Reachable Assertion
Reachable Assertion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.