Skip to content
IoT

CVE-2026-2329

9.3
Critical
EPSS 40%Patch availableFeb 19, 2026

Unauthenticated stack overflow in HTTP API /cgi-bin/api.values.get enables root RCE.

common questions

Is CVE-2026-2329 being exploited?

Not confirmed. CVE-2026-2329 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 40% probability of exploitation in the next 30 days.

How severe is CVE-2026-2329?

CVE-2026-2329 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-2329?

Yes. A fix has been recorded for CVE-2026-2329. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-2329 affect?

CVE-2026-2329 affects GXP1610, GXP1615, GXP1620, GXP1625, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-2329?

Patch when available; restrict API access and monitor.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
GXP1610GXP1615GXP1620GXP1625GXP1628GXP1630
impact

Unauthenticated RCE via HTTP API; attacker gains root on GXP1610/1615/1620/1625/1628/1630.

action required

Immediate action required

affected versions
Grandstream GXP1610
  • affected<= 1.0.7.80
Grandstream GXP1615
  • affected<= 1.0.7.80
Grandstream GXP1620
  • affected<= 1.0.7.80
Grandstream GXP1625
  • affected<= 1.0.7.80
Grandstream GXP1628
  • affected<= 1.0.7.80
Grandstream GXP1630
  • affected<= 1.0.7.80

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free