A reachable assertion vulnerability exists in the Matter SDK (connectedhomeip) before 1.4.0, in the interaction model command processing logic. When an InvokeCommandRequest is sent to a nonexistent endpoint and cluster (e.g., 0x34), the code incorrectly treats the endpoint as valid due to missing checks in CodegenDataModelProvider::Invoke. This causes a VerifyOrDie failure in ProcessCommandDataIB and results in a crash (SIGABRT). The issue has been acknowledged and fixed in a later revision (PR #37207).
CVE-2025-56365
HIGHPre-NVD 7.5Trending — 4 sources updated this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 0.0(none)
- EPSS
- 6.5%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic
[BUG] Crash in ProcessCommandDataIB due to incorrect endpoint validation and VerifyOrDie assertion · Issue #37184 · project-chip/connectedhomeip · GitHub
https://github.com/project-chip/connectedhomeip/issues/37184github_pr
Validate for a valid cluster path when Invoke is called
Fix merged in project-chip/connectedhomeip PR #37207 on 2025-01-31 — awaiting tagged release
https://github.com/project-chip/connectedhomeip/pull/37207generic
GitHub - project-chip/connectedhomeip: Matter (formerly Project CHIP) creates more connections between more objects, simplifying development for manufacturers and increasing compatibility for consumers, guided by the Connectivity Standards Alliance. · GitHub
https://github.com/project-chip/connectedhomeip/Vendor Advisories for CVE-2025-56365(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 14:49 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-07-14 23:23 UTCNVD update
- 2026-07-14 22:25 UTCEG score recompute
- 2026-07-14 22:25 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2025-56365?
CVE-2025-56365 is a high vulnerability published on July 14, 2026. A reachable assertion vulnerability exists in the Matter SDK (connectedhomeip) before 1.4.0, in the interaction model command processing logic. When an InvokeCommandRequest is sent to a nonexistent endpoint and cluster (e.g., 0x34), the code incorrectly treats the endpoint as valid due to missing…
When was CVE-2025-56365 disclosed?
CVE-2025-56365 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-56365 actively exploited?
CVE-2025-56365 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-56365?
CVE-2025-56365 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 0.0.
How do I remediate CVE-2025-56365?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-56365, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-56365
Is Your Infrastructure Affected by CVE-2025-56365?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.