VU#756733: Calix GS7 XGS GS5239XG residential router contains missing authentication vulnerability
Source CERT/CC
Not known to be exploited.
Data as of 17 Sep 2026, 22:18 UTC
Rated Low by Threat Radar from the CERT/CC text · CVSS not yet scored by NVD
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
Public on cve.org; its publication date is not in this record
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
AI-suggested
No mitigation or patch is currently required as Calix has confirmed that the default firmware configuration blocks inbound WAN traffic to TCP port 5000, preventing exploitation. Users do not need to take any action at this time. If users have concerns, they may consider disabling UPnP or filtering inbound traffic to TCP port 5000, but these are not mandated by Calix. The vendor continues to monitor the situation.
Description
The Calix GS7 XGS GS5239XG residential router was initially reported to have a missing authentication vulnerability in its UPnP WANIPConnection service exposed on the WAN interface at TCP port 5000. This could have allowed unauthenticated remote attackers to modify NAT port-forwarding rules, potentially exposing internal LAN devices. However, after thorough investigation and testing by Calix and CERT/CC, it was determined that the default firmware configuration blocks inbound WAN traffic to TCP port 5000, preventing exploitation. No affected customer deployments or required mitigations have been identified. The vulnerability report has been retracted as the issue could not be reproduced under normal conditions.