# CVE-2026-2329: Grandstream GXP1600 VoIP Phones - Unauthenticated stack buffer overflow

> Remote attackers can achieve root-level code execution on Grandstream GXP1600 series VoIP phones via an unauthenticated stack buffer overflow in the HTTP API.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 18 Feb 2026
- **Also known as:** GHSA-r4m3-cm43-fxrj

## What is CVE-2026-2329?

CVE-2026-2329 is a critical memory corruption vulnerability in Grandstream GXP1610, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated stack-based buffer overflow vulnerability exists in the HTTP API endpoint /cgi-bin/api.values.get. A remote attacker can leverage this vulnerability to achieve unauthenticated remote code execution (RCE) with root privileges on a target device. The vulnerability affects all six device models in the series: GXP1610, GXP1615, GXP1620, GXP1625, GXP1628, and GXP1630.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-2329?

It affects 6 products.


Products: Grandstream Gxp1610 Firmware, Grandstream Gxp1615 Firmware, Grandstream Gxp1620 Firmware, Grandstream Gxp1625 Firmware, Grandstream Gxp1628 Firmware, Grandstream Gxp1630 Firmware.

## How do I fix CVE-2026-2329?

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

## Is CVE-2026-2329 being exploited?

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

Public exploit code:

- GrandStream GXP1600 Unauthenticated Remote Code Execution (metasploit)
- https://github.com/VivianUba/grandstream-cve-2026-2329-analysis (github_poc): https://github.com/VivianUba/grandstream-cve-2026-2329-analysis

## Other vulnerabilities in Grandstream GXP1610

- [CVE-2018-17564](https://insights.sbomify.com/CVE-2018-17564/): Missing authorization in n/a (critical 9.8)
- [CVE-2018-17565](https://insights.sbomify.com/CVE-2018-17565/): Command injection in n/a (critical 9.8)
- [CVE-2020-5738](https://insights.sbomify.com/CVE-2020-5738/): Command injection in Grandstream GXP1600 Series (high 8.8)
- [CVE-2020-5739](https://insights.sbomify.com/CVE-2020-5739/): Command injection in Grandstream GXP1600 Series (high 8.8)
- [CVE-2018-17563](https://insights.sbomify.com/CVE-2018-17563/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2329 and fix it if it is affected.

What it is: CVE-2026-2329 is a critical memory corruption vulnerability in Grandstream GXP1610, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2329 exists.

Affected product: Grandstream GXP1610. 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-2026-2329/ (Markdown: https://insights.sbomify.com/CVE-2026-2329/index.md)
```

## Sources

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

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