--- title: "Socket Version 28.0 Release Notes" slug: "socket-version-28-0-release-notes" updated: 2026-11-12T00:10:05Z published: 2026-11-12T00:10:05Z canonical: "knowledge.catonetworks.com/socket-version-28-0-release-notes" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.catonetworks.com/llms.txt > Use this file to discover all available pages before exploring further. # Socket Version 28.0 Release Notes # Socket Version 28.0 Release Notes ## New Features & Updates ## Summary of Minor Versions ## Resolved Issues | ID | Description | Severity | Issue Found In | Issue Resolved In | | --- | --- | --- | --- | --- | | 189423 | After receiving an ICMP "Fragmentation Needed" message, the Socket could retain a reduced tunnel MTU even after the network path recovered, disrupting application connectivity until the Socket was restarted. | Critical | v25 | v28.0 | | 189540 | On Sockets in China, an Internet speed test could fail when the selected test server was unreachable, even when other test servers were accessible. | Medium | v25.0.22236 | v28.0 | | 189858 | After receiving an ICMP "Fragmentation Needed" message, the Socket could retain a reduced tunnel MTU even after the network path recovered, disrupting application connectivity until the Socket was restarted. | Critical | v25 | v28.0 | | 190259 | On Sockets in China, an Internet speed test could fail when the selected test server was unreachable, even when other test servers were accessible. | Medium | v25.0.22236 | v28.0 | | 191937 | On Azure vSocket HA sites, a failover could remove custom Azure tags from the vSocket network interfaces. | Critical | v26.0.22806 | v28.0 | | 194508 | Clearing the configured WAN interface MTU did not restore the default value of 1500. The Socket continued using the previously configured MTU, even after the tunnel reconnected. | Medium | v24.0.21499 | v28.0 | | 194602 | Clearing the configured WAN interface MTU did not restore the default value of 1500. The Socket continued using the previously configured MTU, even after the tunnel reconnected. | Medium | v24.0.21499 | v28.0 | | 198112 | On Azure vSocket HA sites, a failover could remove custom Azure tags from the vSocket network interfaces. | Critical | v26.0.22806 | v28.0 | | 203382 | On X1600 LTE Sockets with automatic SIM failover enabled, a failed SIM switch could leave the cellular modem disconnected until the Socket was restarted. | Medium | v26.0.23517 | v28.0 | | 203660 | On X1600 LTE Sockets with automatic SIM failover enabled, a failed SIM switch could leave the cellular modem disconnected until the Socket was restarted. | Medium | v26.0.23517 | v28.0 | | 205844 | On AWS vSocket HA sites, insufficient free disk space could prevent the secondary vSocket from upgrading. | High | v25.0 | v28.0 | | 206599 | MSS clamping was not applied to bypassed traffic over PPPoE connections, which could cause TCP retransmissions and stalled connections. | High | v26.0 | v28.0 | | 216400 | On AWS vSocket HA sites, insufficient free disk space could prevent the secondary vSocket from upgrading. | High | v25.0 | v28.0 | | 217388 | An X1600 Socket could restart repeatedly and enter a degraded stability state, preventing it from learning routes to other sites and disrupting access to resources. | Critical | v26.0.23517 | v28.0 | | 218538 | LAN Firewall events could omit user identities even when the users were correctly identified in Internet and WAN Firewall events, affecting identity-based LAN access. | High | v27.0.24419 | v28.0 | | 218550 | LAN Firewall events could associate users with incorrect IP addresses, MAC addresses, or device names. Stale user mappings after DHCP address reassignment could cause identity-based rules to block access to internal resources. | High | v27.0.24419 | v28.0 | | 221349 | LAN Firewall events could omit user identities even when the users were correctly identified in Internet and WAN Firewall events, affecting identity-based LAN access. | High | v27.0.24419 | v28.0 | | 221350 | LAN Firewall events could associate users with incorrect IP addresses, MAC addresses, or device names. Stale user mappings after DHCP address reassignment could cause identity-based rules to block access to internal resources. | High | v27.0.24419 | v28.0 |