Security2 publishers2 min readPublished
Calix fiber gateway takes port-forward orders from anyone, and the vendor has not answered
CVE-2026-75501 puts an unauthenticated UPnP control endpoint on the WAN side of a premium ISP gateway. With no patch and no vendor reply, the carriers own the mitigation.
The Watch · Security desk
What happened
- CVE-2026-75501, a missing-authentication bug in Calix GS7 XGS (GS5239XG) routers, lets remote unauthenticated attackers create port-forwarding rules. There is no patch.
- Calix supplies US broadband providers including Cox Communications, Brightspeed, ALLO, CityFibre and Conexon.
- Researcher Brian Khan Quintana tried the vendor on June 7, got nowhere, and took the report to Carnegie Mellon's CERT Coordination Center, which coordinated disclosure.
- In testing from outside his own network, a mapping created with no expiration was still active after the router was power-cycled.
- The recommended step is turning off UPnP in the gateway's admin interface, since no fix exists.
Compiled by The WatchSomething wrong?How this is made
Why it matters
- exposure Cameras, NAS boxes, admin panels and IoT gear behind these gateways become addressable from the public internet without anyone touching the subscriber's credentials.
- constraint Where the carrier has locked the UPnP control, the household cannot act at all, so every fix becomes a support ticket the ISP has to service one line at a time.
- decision Providers now choose between filtering inbound TCP 5000 at their own edge and waiting on firmware from a vendor that has not spoken.
- precedent A CERT/CC-coordinated release with no accompanying vendor statement teaches the next finder that the carrier, not the manufacturer, is the address worth writing to.
MiniUPnPd is built to take orders from the inside. The Internet Gateway Device profile exists so that a console or a client on the LAN can ask the router to open a port for itself, and the daemon complies because the request arrived on an interface the router treats as its own. On the GS5239XG running EXOS/6.6.47 firmware, CERT/CC says that WANIPConnection SOAP service is bound to the public WAN interface on TCP port 5000 with no access controls [2][3]. Authentication was never part of that design. The interface it listened on was the control, and that control is what went missing.
The verb list is what lifts this above nuisance. Unauthenticated requests can add port mappings, delete existing ones, enumerate what is already configured, and ask the router for its external IP address [4]. Enumeration and deletion are the parts that get skipped in summaries: an attacker who can read the mapping table learns what the household has already chosen to expose, and one who can delete entries can break a service the subscriber depends on without ever touching a device inside.
The researcher's own framing is worth quoting because it names the operational property that matters: "One unauthenticated request from anywhere in the world is enough to open a permanent hole through the router's firewall to any device inside the house. No password. No prompt. Nothing on screen. The rule survives a reboot" [10].
Inventory is the first place this gets awkward. The affected model is sold as the GS5239XG and also marketed as the GigaSpire 7u10txg, a new premium unit pairing Wi-Fi 7 with an integrated XGS-PON terminal [8]. Any asset search keyed to one of those two strings will undercount the fleet, and support records for carrier-supplied CPE rarely agree on which name got typed [3].
Then the mitigation. The advice on offer is to switch off UPnP in the gateway's administrative interface under Advanced then Security then UPnP, which also turns off automatic port opening for games that expect it, though specific ports can still be forwarded by hand [11][12]. CERT/CC adds that the setting is sometimes locked, in which case the subscriber is told to ask their ISP to disable it [13]. That is the whole subscriber-side toolkit, and on a locked unit it is empty [1]. What remains is upstream: the vulnerable service is reachable as inbound TCP 5000 on the WAN, so filtering that port at the edge removes reachability without a firmware change [2]. That is a decision only Cox, Brightspeed, ALLO and the rest can make, and it is the only one currently available.
What to watch
- A Calix advisory or an EXOS build past 6.6.47 that closes the WAN-side listener, and whether it arrives as a carrier push or a subscriber download.
- Any confirmation from Cox, Brightspeed or ALLO that inbound TCP 5000 is filtered at their edge, or that the UPnP toggle has been unlocked for subscribers.
- Internet-wide scan counts for gateways answering SOAP on port 5000, which would turn an unknown installed base into a countable one.