dbcve.org
Gxp1610 FirmwareOperating system · Grandstream

CVE-2026-2329

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-18
Fix available
A fix is available. Upgrade to 1.0.7.81 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stack-based buffer overflow in the HTTP API endpoint /cgi-bin/api.values.get on Grandstream GXP16xx VoIP phones allows unauthenticated remote attackers to achieve root-level RCE by overflowing a stack buffer in the api.values.get handler.

MitigationApply vendor firmware updates when available; until then, disable or firewall the HTTP API endpoints and restrict remote access to device management interfaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gxp1610 FirmwareOperating system
Affected:< 1.0.7.81
Gxp1615 FirmwareOperating system
Affected:< 1.0.7.81
Gxp1620 FirmwareOperating system
Affected:< 1.0.7.81
Gxp1625 FirmwareOperating system
Affected:< 1.0.7.81
Gxp1628 FirmwareOperating system
Affected:< 1.0.7.81
Gxp1630 FirmwareOperating system
Affected:< 1.0.7.81

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device web interface or check the device label to confirm it is a Grandstream GXP1610, GXP1615, GXP1620, GXP1625, GXP1628, or GXP1630 VoIP phone.
    Affected if The device is one of these six models.
  2. Check the firmware version
    Log into the device web interface and navigate to Status > System Info, or use the device API to retrieve the firmware version. Compare the version number to 1.0.7.81.
    Affected if The installed firmware version is less than 1.0.7.81.
  3. Verify HTTP API accessibility
    Attempt to access the endpoint http://<device_ip>/cgi-bin/api.values.get using a web browser or curl command. No authentication should be required.
    Affected if The endpoint responds without requiring credentials.
  4. Confirm the API functionality
    Send a GET request to /cgi-bin/api.values.get and verify the device returns a response. The vulnerability exists in this unauthenticated endpoint.
    Affected if The endpoint is reachable and returns a response without authentication.

The device is affected if it is a Grandstream GXP1610/1615/1620/1625/1628/1630 running firmware below version 1.0.7.81 and the /cgi-bin/api.values.get endpoint is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.7.81 or later
Fixed in 1.0.7.81
Vendor patch github.com →
Interim mitigation

Apply vendor firmware updates when available; until then, disable or firewall the HTTP API endpoints and restrict remote access to device management interfaces.

Recommended fix High confidence

Firmware version 1.0.7.81 or later for GXP1610/1615/1620/1625/1628/1630

  1. 1. Download the firmware update from the official Grandstream firmware repository at firmware.grandstream.com
  2. 2. Ensure you select the correct firmware version 1.0.7.81 (or later) for your specific device model (GXP1610, GXP1615, GXP1620, GXP1625, GXP1628, or GXP1630)
  3. 3. Access the device web interface and navigate to the firmware upgrade section
  4. 4. Upload the downloaded firmware file (.bin) to the device
  5. 5. Wait for the upload to complete and for the device to reboot automatically
  6. 6. After reboot, verify the firmware version has been updated to 1.0.7.81 or later in the device status page
  7. 7. Confirm the /cgi-bin/api.values.get endpoint is no longer exposed or has been patched
Caveat Review Grandstream release notes for any configuration changes or feature modifications between your current version and 1.0.7.81

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gxp1610 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2329 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data