# CVE-2025-8414: Zigbee Green Power Host Buffer Overflow Vulnerability

> A buffer overflow in Zigbee EZSP Host Applications allows arbitrary code execution if an attacker has network key access.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA: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:** 17 Oct 2025
- **Updated:** 17 Oct 2025
- **Also known as:** GHSA-9ppj-5fv3-g9qh

## What is CVE-2025-8414?

CVE-2025-8414 is a critical memory corruption vulnerability in silabs.com Gecko SDK, published on 17 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Due to improper input validation, a buffer overflow vulnerability is present in 

Zigbee EZSP Host Applications. If the buffer overflows, stack corruption is possible. In certain

conditions, this could lead to arbitrary code execution. Access to a network key is required to exploit this vulnerability.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2025-8414 being exploited?

There is no known exploitation of CVE-2025-8414 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8414 is a critical memory corruption vulnerability in silabs.com Gecko SDK, published on 17 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8414 in the wild and no public exploit code.

Affected product: silabs.com Gecko SDK. 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-8414/ (Markdown: https://insights.sbomify.com/CVE-2025-8414/index.md)
```

## Sources

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

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