| NC-187231 |
Antivirus |
The antivirus service failed to start. |
| NC-180066 |
Antivirus |
SAVI and AVIRA pattern updates failed, causing the Antivirus service to stop. |
| NC-177519 |
Antivirus |
"Unscannable" notifications were generated after upgrading to SFOS 22.0 while antivirus patterns were being updated. |
| NC-180414 |
ATP Framework |
Previously blocked IP addresses continued to be detected as threats after being removed from the threat intelligence list. |
| NC-185491 |
Authentication |
Filtering users by user group on the Users page failed in some cases. |
| NC-184278 |
Authentication |
Users belonging to multiple OUs couldn't authenticate with the VPN Portal on their first attempt. |
| NC-182021 |
Authentication |
UI filter for user groups didn't work. |
| NC-181942 |
Authentication |
AD server configuration in the firewall didn't accept domain names with top-level domains longer than seven characters |
| NC-180824 |
Authentication |
New Active Directory users who were members of a secondary AD group failed to sign in to the VPN portal. |
| NC-176806 |
Authentication |
Microsoft Entra ID SSO failed due to missing intermediate CA certificates in the firewall. |
| NC-176367 |
Authentication |
"null" entries appeared in the Live user list in an HA cluster after a firmware upgrade. |
| NC-176222 |
Authentication |
STAS sign in was affected after an upgrade to SFOS 22.0 GA. |
| NC-176109 |
Authentication |
Repeated XML API authentication with MFA turned on prevented administrator sign-ins to the web admin console and the API. |
| NC-172558 |
Authentication |
User portal showed the Microsoft Entra ID SSO option when it wasn't configured for the portal and returned a 404 error when users selected it. |
| NC-171261 |
Authentication |
SSL VPN SSO authentication failed after HA failover and failback. |
| NC-167549 |
Authentication |
LDAP authentication accepted usernames with trailing spaces and created duplicate user entries. |
| NC-167173 |
Authentication |
Captive portal sign-out settings didn't accurately describe Microsoft Entra ID SSO behavior. |
| NC-166341 |
Authentication |
Microsoft Entra ID users were added to SSL VPN policies after VPN portal sign-in, even when their group was already assigned to the policy. |
| NC-162171 |
Authentication |
L2TP VPN authentication using MS-CHAP or MS-CHAPv2 didn't include the configured NAS-Identifier. |
| NC-161118 |
Authentication |
Users could access the internet with on-premises AD authentication but not with Microsoft Entra ID SSO. |
| NC-160157 |
Authentication |
A user's last access time persisted after user deletion and was shown when the user signed in again. |
| NC-148705 |
Authentication |
QoS policy wasn't applied to clientless users when their count exceeded 3,000. |
| NC-176113 |
Backup-Restore |
Failed to restore a backup created on an HA device because of an interface mapping mismatch. |
| NC-181147 |
Bridge |
DHCP leasing failed in bridge mode. |
| NC-175860 |
Certificates |
A remote access IPsec connection failed after HA failover when Appliance Certificate was regenerated. |
| NC-182222 |
Clientless Access |
Users with numerical usernames couldn't establish SSL VPN connections after upgrading to SFOS 22.0 MR1. |
| NC-183421 |
CM |
Some Sophos Fusion transactions remained stuck in "In progress" after the firewall restarted. |
| NC-181175 |
CM |
Group policy push from Sophos Fusion remained pending and wasn't applied to firewalls. |
| NC-180529 |
CM |
Auxiliary HA device deregistered from Sophos Fusion. |
| NC-177526 |
CM |
Firewall health check failed to load data. |
| NC-183013 |
Config Migration Framework |
Upgrade from SFOS 22.0 MR1 to MR2 failed because of Lets_Encrypt CA. |
| NC-182765 |
CP 2.0 HA |
Failed to assign port 6222 to Admin console HTTPS port. |
| NC-181687 |
CP 2.0 HA |
SSL VPN policy creation failed with an internal server error. |
| NC-181331 |
CP 2.0 HA |
The firewall entered failsafe mode due to a full configuration partition. |
| NC-187233 |
CSC |
Creating an AP VXLAN was slower than expected in SFOS 22.0 MR2. |
| NC-180152 |
CSC |
Interface updates took longer in SFOS 22.0 than in 21.5. |
| NC-188373 |
DNS |
DNS Protection failed after an upgrade. |
| NC-186632 |
DNS |
Test name resolution continued to use fallback DNS servers after fallback was turned off. |
| NC-180219 |
DDNS |
DDNS with Cloudflare failed after an upgrade to SFOS 22.0 MR1. |
| NC-175885 |
DNS |
The Name lookup tool limited hostnames to 40 characters. |
| NC-175952 |
DHCP |
The dhcpd process remained in exiting status after restoring a partial DHCP server configuration. |
| NC-190566 |
Dynamic Routing (OSPF) |
OSPF neighbor connections over route-based IPsec tunnels with an Any-Any SD-WAN route failed. |
| NC-183979 |
Email |
An XGS appliance underwent an extended reboot during an upgrade to SFOS 22.0 MR2 due to a large mail spool. |
| NC-179341 |
Email |
Some emails bounced after a firmware upgrade to SFOS 22.0 GA. |
| NC-177930 |
Email |
Emails were stuck in mail spool due to a mailpoller crash. |
| NC-173014 |
Email |
Emails containing reports failed smart host authentication. |
| NC-171602 |
Email |
Firewall notification emails failed DKIM validation. |
| NC-184219 |
Firewall |
An OSPF outage occurred after HA failover on SFOS 22.0 MR1. |
| NC-184117 |
Firewall |
With STAS configured, users were prompted to sign in to the captive portal again after successful authentication. |
| NC-183728 |
Firewall |
Web policies with user-group filters weren't applied to SATC traffic in active-active HA mode. |
| NC-183679 |
Firewall |
Traffic counters for all firewall rules remained at zero. |
| NC-183447 |
Firewall |
Auxiliary HA device experienced a kernel crash when processing IPv6 multicast traffic. |
| NC-182532 |
Firewall, SDWAN Routing |
The policy route service stopped running. |
| NC-182441 |
Firewall |
The firewall entered failsafe mode during a firmware upgrade. |
| NC-182434 |
Firewall |
The firewall experienced a kernel crash when processing multicast traffic. |
| NC-181968 |
Firewall |
Querying large IP sets resulted in an internal loop error. |
| NC-181741 |
Firewall |
Unauthenticated user traffic was dropped every hour. |
| NC-181344 |
Firewall |
First Alive NAT didn't fail back to the first server when it became available again. |
| NC-180974 |
Firewall |
A kernel crash in sdwan_profile resulted in HA failover. |
| NC-180960 |
Firewall |
The firewall entered failsafe mode after upgrading to SFOS 22.0 GA when an empty service group was configured in rules and policies. |
| NC-180464 |
Firewall |
SMTP traffic configured with DNAT was incorrectly dropped after an upgrade to SFOS 22.0. |
| NC-178996 |
Firewall |
Packet capture showed an incorrect gateway interface for traffic routed through an SD-WAN route. |
| NC-178903 |
Firewall |
SATC users couldn't access the internet after an upgrade to SFOS 22.0 GA. |
| NC-178413 |
Firewall |
An empty value in Services caused an ipset failure and the firewall to start in failsafe mode. |
| NC-178354 |
Firewall |
A kernel crash occurred during SD-WAN rule matching. |
| NC-177934 |
Firewall |
The firewall entered failsafe mode after an upgrade to SFOS 22.0 GA. |
| NC-177047 |
Firewall |
ZTNA agentless applications behind WAF became inaccessible after upgrading the gateway firewall to SFOS 22.0 GA. |
| NC-176846 |
Firewall |
Log Viewer showed "No Heartbeat" in firewall logs when the endpoint device's actual Security Heartbeat status was green. |
| NC-176836 |
Firewall |
Failed to remove an SNAT rule for system-generated traffic. |
| NC-176582 |
Firewall |
The firewall restarted automatically when processing malformed IPv6 neighbor solicitation or neighbor advertisement packets. |
| NC-176532 |
Firewall |
Failed to ping external IP addresses from Diagnostics through a backup WAN after upgrading to SFOS 22.0 GA. |
| NC-175949 |
Firewall |
Firewall rules created through the firewall API couldn't be deleted, and an incorrect message appeared stating that they were created by a Sophos Fusion administrator. |
| NC-175933 |
Firewall |
The auxiliary firewall restarted repeatedly after an HA status change, causing a network outage. |
| NC-173054 |
Firewall |
SSL VPN users were shown a CAPTCHA when accessing the web admin console even when CAPTCHA was disabled for the VPN zone. |
| NC-169537 |
Firewall |
Packet capture process consumed high CPU when processing IPv6 traffic with ESP or AH headers. |
| NC-169452 |
Firewall |
Export of firewall rules failed. |
| NC-170200 |
Firmware Management |
Firmware upgrades failed when multiple upgrade attempts were made within a few minutes. |
| NC-188293 |
FW AI Assistant |
REST API name filters didn't filter the returned objects as expected. |
| NC-182024 |
Gateway Management |
Failed to update a WAN gateway failover rule when the gateway name and monitor object name didn't match. |
| NC-186809 |
HA |
The web admin console and VPN portal were unreachable due to a certificate synchronization failure on the auxiliary appliance when some certificate filenames began with two consecutive periods. |
| NC-183680 |
HA |
The auxiliary device entered failsafe mode during an HA status change. |
| NC-183651 |
HA |
Endpoint devices with odd IP addresses couldn't access the internet through a VLAN on a bridge in active-active HA. |
| NC-181343 |
HA |
The auxiliary device entered failsafe mode while HA was being established. |
| NC-177467 |
HA |
The auxiliary device failed to start due to an excessive number of concurrent unauthenticated SSH connection requests. |
| NC-176051 |
HA |
HA wasn't established after an abrupt power cycle. |
| NC-173031 |
HA |
Application policies imported to an HA cluster didn't automatically synchronize to the auxiliary device. |
| NC-169390 |
HA |
Failed to create firewall rules because of synchronization failure between HA devices. |
| NC-182263 |
Hotspot |
The hotspot voucher export contained duplicate voucher codes when more than 20 vouchers were created in a single batch. |
| NC-191261 |
Interface Management |
Couldn't add or update DHCP Option 43 for DHCPv4 servers. |
| NC-177599 |
Interface Management |
The mtr command failed in SFOS 22.0 GA. |
| NC-183871 |
IPsec |
Create firewall rule was automatically selected after being cleared when configuring a route-based IPsec connection. |
| NC-180433 |
IPsec |
The firewall crashed repeatedly when multicast traffic was sent through a VPN tunnel. |
| NC-178704 |
IPsec |
IPsec tunnels didn't reconnect automatically after a power outage. |
| NC-178305 |
IPsec |
A WAN gateway remained down even when its health check succeeded. |
| NC-178121 |
IPsec |
Site-to-site IPsec connections moved to incorrect positions within a failover group after drag-and-drop reordering in SFOS 22.0 GA. |
| NC-177635 |
IPsec |
After an upgrade to SFOS 22.0 GA, incoming IPsec traffic between Sophos Firewall and certain third-party routers didn't work. |
| NC-171719 |
IPsec |
An SD-WAN routing issue occurred with ESP traffic. |
| NC-177844 |
IPS Engine |
The primary HA device temporarily changed to standalone status during an IPS restart, causing a brief internet outage. |
| NC-183859 |
IPS Ruleset Management |
A virtual auxiliary device entered failsafe mode during startup due to a signature database timezone configuration error. |
| NC-176587 |
IPS Ruleset Management |
An IPS policy created from a firewall rule didn't appear in the IPS policy list, and the firewall rule couldn't be saved or canceled. |
| NC-166726 |
IPS Ruleset Management |
The auxiliary device entered failsafe mode after an HA failover following an upgrade from SFOS 20.0 MR1 to 21.5 MR1. |
| NC-161000 |
IPS Ruleset Management |
IPS and application signature updates failed when there was no Network Protection license. |
| NC-184931 |
Logging Framework |
Dynamic DNS update information wasn't shown in the web admin console. |
| NC-182435 |
Logging Framework |
Control center showed incorrect bandwidth usage values. |
| NC-181730 |
Logging Framework |
Executive Report failed to download as a PDF when the duration was set to one month. |
| NC-180110 |
Logging Framework |
The primary HA device entered failsafe mode because the logging daemon failed to start. |
| NC-180082 |
Logging Framework |
SD-WAN and SD-WAN SLA trend reports appeared blank in Central Firewall Reporting. |
| NC-178745 |
Logging Framework |
An HA device restarted automatically due to out-of-memory condition. |
| NC-172912 |
Logging Framework |
The system graph flickered. |
| NC-171847 |
Logging Framework |
The firewall restarted unexpectedly. |
| NC-165769 |
Logging Framework |
Resolved an issue related to KBps versus Kbps units under the system interface graph. |
| NC-160238 |
Logging Framework |
High disk usage caused high system load and network interruption. |
| NC-152553 |
Logging Framework |
Recovery mechanism failed for active.db. |
| NC-151296 |
Logging Framework |
Web filter logs didn't appear when DPI was turned on. |
| NC-151089 |
Logging Framework |
The executive report download failed when the date range was set to one day. |
| NC-185420 |
NDR intrusion detection |
The firewall didn't respond to SNMP requests after an XGS 116 backup was restored to an XGS 118 appliance. |
| NC-178141 |
Netfilter Utils |
Specific ICMP error messages were dropped by local ACL rules after upgrading to SFOS 22.0 GA. |
| NC-180933 |
NFP-Firewall |
Administrators couldn't sign in to the web admin console. |
| NC-179604 |
NFP-Firewall |
The firewall generated unnecessary tuple-related messages in the syslog when firewall acceleration was turned on. |
| NC-177769 |
NFP-Firewall |
The eBPF service became unresponsive after a pattern update. |
| NC-176855 |
NFP-Firewall |
IPv6 throughput issues occurred over a route-based IPsec VPN connection. |
| NC-177441 |
Postgres |
After an upgrade to SFOS 22.0 GA, the initial primary device entered failsafe mode. |
| NC-180255 |
PPPoE |
After the active device became faulty and HA failover occurred, it re-established its PPPoE connection, disrupting internet connectivity on the current active device. |
| NC-178197 |
QoS |
Application traffic intermittently stopped when an application-based bandwidth policy was applied. |
| NC-181808 |
RED |
Traffic was blocked after a RED device was reset and reprovisioned because stale RED_DEVICE_DROP entries weren't removed. |
| NC-178906 |
RED |
The firewall entered failsafe mode with the error "Failed to start Red server service". |
| NC-184632 |
Reporting |
The Events report showed numbers instead of "Notice" in the severity column for "New firmware is available for installation" events. |
| NC-180313 |
Reporting |
Custom logos appeared at an incorrect resolution in scheduled reports sent over email. |
| NC-172020 |
Reporting |
Firewalls without on-box reporting sent daily emails with an empty Traffic dashboard PDF report. |
| NC-169646 |
Reporting |
On-demand PDF reports contained incorrect charts and tables when generated in Chrome. |
| NC-155252 |
Reporting |
Heavy disk I/O operations caused CPU spikes, resulting in intermittent internet outages of up to one minute. |
| NC-186411 |
SDWAN Routing |
After a firmware upgrade to SFOS 22.0 MR1, some SD-WAN routes incorrectly applied DSCP matching even though it was turned off on the web admin console. |
| NC-185846 |
SDWAN Routing |
TFTP return traffic over a route-based IPsec tunnel was routed through the WAN interface instead of the tunnel interface, causing TFTP provisioning to fail. |
| NC-182935 |
SDWAN Routing, VPN |
A network interruption occurred while a customer added a new site to the SD-WAN group. |
| NC-177603 |
SDWAN Routing, VPN |
Adding a new site to an SD-WAN group temporarily disrupted network connectivity at other sites in the group. |
| NC-176012 |
SecurityHeartbeat |
Missing heartbeat was reported when two endpoints shared the same docking station or USB interface. |
| NC-164973 |
Sentry framework |
Stale Sentry mini-dump files from cstad caused the /var partition to fill, leading to high disk utilization. |
| NC-181904 |
SFOS-Central |
Failed to release quarantine emails when the firewall was accessed through Sophos Fusion. |
| NC-183165 |
Snort-app |
The firewall failed to start after a firmware upgrade because a missing signature database table prevented the Garner service from starting. |
| NC-180226 |
Spoofing |
The web admin console didn't show an error when a duplicate MAC address was added under Spoof protection trusted MAC. |
| NC-182395 |
SSLVPN |
SSL VPN split tunnels incorrectly routed traffic to FQDN hosts that weren't configured as permitted network resources. |
| NC-179224 |
SSLVPN |
Communication through site-to-site SSL VPN stopped after an HA failover, even though the tunnel remained active. |
| NC-177903 |
SSLVPN |
SSL VPN service restarted periodically with certain configurations. |
| NC-140332 |
SSLVPN |
After seven to eight hours of SSL VPN tunnel connectivity, Linux endpoint devices encountered authentication failures when static IP addresses were configured. |
| NC-181299 |
Static Routing |
The SFOS GeoIP database incorrectly mapped an IP address to United Kingdom instead of Germany. |
| NC-165730 |
Static Routing |
Supernetting didn't work for 10.96.255.0/24 when the subnet was changed to 22 or lower. |
| NC-185225 |
Synchronized App Control |
After a firmware upgrade, the firewall incorrectly reported insufficient storage while optimizing Synchronized Application Control data. |
| NC-182635 |
Synchronized App Control |
Repeated application path updates triggered additional application filter refreshes, causing high CPU utilization. |
| NC-186948 |
UI Framework |
Clicking the Cloud Applications widget on the Control center didn't open the Cloud Applications page. |
| NC-181575 |
UI Framework |
The time field in Schedule appeared incorrectly. |
| NC-171424 |
UI Framework |
Deleting the only exception on the last page caused the Web Exceptions page to appear empty instead of showing the previous page. |
| NC-189640 |
WAF |
WAF became slow and eventually stopped working. |
| NC-188249 |
WAF |
WAF failed to start when a web server rule used a hostname containing non-ASCII characters. |
| NC-180587 |
WAF |
After successful form-based authentication, WAF redirected users to the site path instead of the originally requested URL. |
| NC-180200 |
WAF |
WAF stopped during nightly license synchronization in Home Edition firewalls. |
| NC-179812 |
WAF |
The Let's Encrypt certificate failed to renew automatically. |
| NC-177457 |
WAF |
When WAF debugging was turned on, the password was visible in reverseproxy.log. |
| NC-177201 |
WAF |
OTP code wasn't stripped from the password before it was forwarded to the backend. |
| NC-176796 |
WAF |
An invalid Let's Encrypt certificate in a WAF rule caused all WAF connections to stop working. |
| NC-176788 |
WAF |
The ResponseFieldSize value reverted to the default value when the certificate was changed in a WAF rule. |
| NC-181286 |
Web |
Links opened from Google Workspace apps intermittently failed to load with an HTTP 400 error. |
| NC-177257 |
Web |
The local TLS exclusion list couldn't be edited on XGS 88, causing Sophos Fusion synchronization to fail. |
| NC-176679 |
Web |
Antivirus service stopped after an upgrade to SFOS 22.0 GA when TCP 9090 was already in use. |
| NC-175950 |
Web |
Application filter logs weren't generated for some applications. |
| NC-174477 |
Web |
httplogd sent corrupted data to garner when the bytes sent weren't a complete record. |
| NC-182336 |
WebInSnort |
Temporary antivirus scanning files accumulated and caused the /var partition to reach 100% utilization. |
| NC-179938 |
WebInSnort |
The IPS service stopped working and couldn't be restarted when web policy files became corrupted. |
| NC-167019 |
WebInSnort |
High CPU utilization occurred due to Snort when VEEAM traffic didn't have an exception. |
| NC-182994 |
Wireless |
The firewall incorrectly logged new firmware alerts for APX access points after a restart even when the firmware hadn't changed. |
| NC-180133 |
Wireless |
APX access points lost their registration with the firewall during a firmware upgrade and became inactive. |