# CVE-2025-56364: Null dereference in n/a

> An attacker can cause a denial of service in Matter SDK devices by sending an InvokeCommand without initializing the destination group ID, triggering a crash.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-3xhc-5w7c-ppw7

## What is CVE-2025-56364?

CVE-2025-56364 is a medium-severity vulnerability in n/a, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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 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.

Weakness: CWE-457 (Use of Uninitialized Variable)

## Which versions are affected by CVE-2025-56364?

It affects 1 product.


Products: Csa-Iot Matter.

## How do I fix CVE-2025-56364?

No fix has been published for CVE-2025-56364 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-56364 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56364 exists.

## Other vulnerabilities in n/a

- [CVE-2024-3297](https://insights.sbomify.com/CVE-2024-3297/): Session establishment lock-up during replay of CASE Sigma1 messages (medium 6.5)
- [CVE-2025-56361](https://insights.sbomify.com/CVE-2025-56361/): Denial of service in n/a (medium 5.7)
- [CVE-2025-56362](https://insights.sbomify.com/CVE-2025-56362/): Denial of service in n/a (medium 5.7)
- [CVE-2025-56363](https://insights.sbomify.com/CVE-2025-56363/): Null dereference in n/a (medium 5.7)
- [CVE-2025-56365](https://insights.sbomify.com/CVE-2025-56365/): Denial of service in n/a (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-56364 and fix it if it is affected.

What it is: CVE-2025-56364 is a medium-severity vulnerability in n/a, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56364 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-56364/ (Markdown: https://insights.sbomify.com/CVE-2025-56364/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-56364
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-56364
- OSV: https://osv.dev/vulnerability/CVE-2025-56364

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-56364/
Summaries are generated and may contain mistakes; the official description above is the record.