CyberSecBulletin
CVE-2026-2329NVD status: Analyzed

GXP1610: Stack-based Buffer Overflow

Published Updated By the CyberSecBulletin desk

CVE-2026-2329 is a critical-severity stack-based buffer overflow vulnerability in GXP1610 from Grandstream, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected GXP1610 versions: 1.0.7.80 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 41.7% chance of exploitation within 30 days, which is in the top 1.29% of all scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Gxp1610 Firmware to 1.0.7.81 or a later version.
  2. Update Gxp1615 Firmware to 1.0.7.81 or a later version.
  3. Update Gxp1620 Firmware to 1.0.7.81 or a later version.
  4. Read the advisory on psirt.grandstream.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
GrandstreamGXP16101.0.7.80 and earlierNot stated
GrandstreamGXP16151.0.7.80 and earlierNot stated
GrandstreamGXP16201.0.7.80 and earlierNot stated
GrandstreamGXP16251.0.7.80 and earlierNot stated
GrandstreamGXP16281.0.7.80 and earlierNot stated
GrandstreamGXP16301.0.7.80 and earlierNot stated
GrandstreamGxp1610 Firmwarebefore 1.0.7.811.0.7.81
GrandstreamGxp1615 Firmwarebefore 1.0.7.811.0.7.81
GrandstreamGxp1620 Firmwarebefore 1.0.7.811.0.7.81
GrandstreamGxp1625 Firmwarebefore 1.0.7.811.0.7.81
GrandstreamGxp1628 Firmwarebefore 1.0.7.811.0.7.81
GrandstreamGxp1630 Firmwarebefore 1.0.7.811.0.7.81

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.09.3CriticalCNA (rapid7.com)
CVSS 3.19.8CriticalNVD

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Stack-based Buffer Overflow

The product writes past the end of a buffer that was allocated on the stack.

How developers prevent this class of flaw

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
  • Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Implement and perform bounds checking on input.

More Stack-based Buffer Overflow vulnerabilities (CWE-121)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Stack-based Buffer Overflow vulnerabilities

Spotted an error? Tell us.