8.2.41 Release Notes

Release Date: 5 November 2026

Release Notes Last Updated: 5 November 2026

Upgrade guidance for this security fix release: This release applies a mitigation for a Linux kernel vulnerability (CVE-2026-98432) on gateways. The Controller receives the kernel fix through operating system updates, so you do not need to upgrade the Aviatrix software first. The fix takes effect only after you reboot the Controller, so check the Controller kernel version and reboot the Controller as soon as you can. Gateways running 8.1.x or later are mitigated shortly after the Controller is upgraded. When you have a maintenance window, upgrade the Controller to 8.2.41, and then upgrade the gateways to 8.2.41. For how to check the kernel version and the fixed versions, see the PSIRT Advisories.

Corrected Issues in Aviatrix Release 8.2.41

This release applies a mitigation for the following CVE advisory, detailed on the PSIRT Advisories page:

CVE-2026-98432: Linux kernel IPv4 TCP race condition.

Known Issues in Aviatrix Release 8.2.41

Issue Description

Issue	Description
AVX-72940	Creating a new gateway with the same name as an existing gateway may cause local files of the existing gateway to be deleted when the creation fails. The existing gateway name disappears from the Controller CLI once this occurs. This can break SSH access to the existing gateway. Impact: SSH access to the existing gateway may stop working Gateway recovery may require manual intervention Affected Scenario: Gateway creation using a name that already exists. Workaround: Do not reuse gateway names. Contact Aviatrix Support if recovery is required.
AVX-73436	When using the update_spoke_vpc_route_table API to onboard an Azure route table, the default route (0.0.0.0/0) is not programmed in the spoke VNET route table if the Spoke Gateway has learned the default route from any of the following sources: An attached Egress Transit Gateway (Transit with egress functionality enabled) A Transit Gateway that learned the default route via an external Site-to-Cloud (S2C) connection (for example, from an on-premises network or third-party appliance advertising 0.0.0.0/0 over IPSec/BGP) Another Spoke Gateway that is propagating the default route within the Aviatrix network In all of the above cases, although the Spoke Gateway has successfully learned and installed the default route in its own routing table, the route is not re-programmed into the associated Azure VNET route table during the onboarding operation. Impact: Default route (0.0.0.0/0) is not installed in the onboarded Azure spoke VNET route table. Traffic that depends on the default route, including traffic destined for the internet through an egress transit, for on-premises networks through an S2C-connected transit, or for another spoke, may not be routed correctly from the Azure VNET. Workaround: Manually add the default route to the Azure route table. Contact Aviatrix Support for assistance.
AVX-75452	In Azure environments, when Distributed Cloud Firewall (DCF) Security Group Orchestration attaches a Network Security Group (NSG) to a subnet, the subnet name is changed to all lowercase. Although Azure resource names are generally case-insensitive, this modification causes issues with Infrastructure as Code tools such as Terraform, which treat resource names as case-sensitive. Terraform may flag affected subnets for replacement, potentially disrupting existing deployments. Impact: Subnet names in Azure are modified to lowercase when Security Group Orchestration attaches NSGs Terraform plans may show unexpected resource replacements for affected subnets Customer naming conventions in the cloud may be altered without consent Workaround: In Terraform, add a `lifecycle` block with `ignore_changes` for `subnet_id` (as well as `id` in the `azurerm_subnet` resource) to prevent forced resource replacement. Note that this workaround does not restore the original subnet name casing.
AVX-75607	Gateway launch may fail with a `tls: bad certificate` error when pulling container images. The Controller’s registry TTL eviction (garbage collection) may fire while images are being downloaded to the gateway, corrupting in-flight blob transfers. The gateway’s container initialization cannot complete, and an internal identity-helper service on the gateway exits with code 125. Impact: Gateway creation fails with tls: bad certificate or unexpected EOF errors during container image pull The gateway’s identity-helper service crash-loops with exit code 125 Manual intervention is required to recover Workaround: Restart the Controller’s core application service to reset the registry state, then retry gateway creation. Contact Aviatrix Support for assistance.
AVX-79012	Some gateways may become stuck in a failed configuration-push state for an extended period after an Image Upgrade to Aviatrix 10.0.0 (from 9.0.10). This has been observed primarily on lower-memory gateway instance types (for example, AWS t3.micro). Impact: Affected gateways may show a "Not Up-To-Date" config status and a down backup tunnel hours after the image upgrade completes. The root cause is a Distributed Cloud Firewall (DCF) configuration push failure caused by insufficient available memory on memory-constrained instance types. Workaround: Retry the gateway Image Upgrade. If the gateway remains stuck in this state, increase the gateway’s instance size for additional memory headroom, or contact Aviatrix Support.
AVX-79521	On Controller versions prior to 10.1.0, it is possible to onboard multiple Aviatrix access accounts that map to the same underlying cloud service provider (CSP) account. Because several Controller features assume a one-to-one relationship between an Aviatrix access account and a CSP account, duplicate access accounts can lead to unpredictable configuration and operational behavior. Duplicate is defined per CSP as follows: AWS (including AWS GovCloud and AWS China): same account number, for both IAM role and access/secret key authentication. Azure (including Azure Government and Azure China): same subscription. GCP: same project. OCI (including OCI Government): same tenancy and compartment combination. Alibaba: same account number. Starting in Controller 10.1.0, the Controller blocks new onboarding of duplicate access accounts across all supported CSPs. Existing duplicate access accounts continue to operate as-is and are not automatically removed. Impact: New duplicate access accounts can still be onboarded on Controller versions prior to 10.1.0. Environments that already have duplicate access accounts may see inconsistent behavior in features that assume a unique CSP account per Aviatrix access account. Workaround: Onboard only one Aviatrix access account per underlying CSP account. If duplicate access accounts have already been onboarded and are causing issues, contact Aviatrix Support for assistance with identifying and removing the duplicates.
AVX-80977	A VPN user’s profile assignment could appear as N/A immediately after the user was attached to a profile through the API, until the user’s next reconnection. Impact: The user’s profile displays as N/A until the user’s next reconnection, even though the profile attachment succeeded. This can cause confusion when auditing or verifying profile-based access policies shortly after attachment. Workaround: Have the affected user reconnect to update the displayed profile assignment. Contact Aviatrix Support for assistance.
AVX-81230	Enabling both Policy-Based Routing (PBR) and NAT logging under User VPN settings can cause high CPU utilization on the User VPN gateway during data-plane traffic. The high CPU usage occurs because NAT log entries generated by PBR are written to the gateway’s serial console. Impact: User VPN gateways with both PBR and NAT logging enabled may experience elevated CPU utilization while passing data-plane traffic, which can degrade VPN gateway performance. Workaround: Disable NAT logging on the affected User VPN gateway. If NAT logging must remain enabled, contact Aviatrix Support to apply a backend workaround.
AVX-81576	During a Gateway resize operation (for example, changing the Gateway’s underlying instance or VM size), the Gateway can experience a temporary period of traffic loss during the resize. This has been observed during testing on GCP, AWS, and Azure Gateways, where a resize between certain instance sizes produced approximately 2 minutes of packet loss. Impact: A Gateway resize can result in a brief traffic interruption, observed at approximately 2 minutes in testing. This has been confirmed to occur on GCP, AWS, and Azure Gateways. Workaround: No workaround is currently available. A fix is planned for a future 10.1.x maintenance release.

AVX-72940

Creating a new gateway with the same name as an existing gateway may cause local files of the existing gateway to be deleted when the creation fails. The existing gateway name disappears from the Controller CLI once this occurs. This can break SSH access to the existing gateway.

Impact:

SSH access to the existing gateway may stop working
Gateway recovery may require manual intervention

Affected Scenario:

Gateway creation using a name that already exists.

Workaround:

Do not reuse gateway names. Contact Aviatrix Support if recovery is required.

AVX-73436

When using the update_spoke_vpc_route_table API to onboard an Azure route table, the default route (0.0.0.0/0) is not programmed in the spoke VNET route table if the Spoke Gateway has learned the default route from any of the following sources:

An attached Egress Transit Gateway (Transit with egress functionality enabled)
A Transit Gateway that learned the default route via an external Site-to-Cloud (S2C) connection (for example, from an on-premises network or third-party appliance advertising 0.0.0.0/0 over IPSec/BGP)
Another Spoke Gateway that is propagating the default route within the Aviatrix network

In all of the above cases, although the Spoke Gateway has successfully learned and installed the default route in its own routing table, the route is not re-programmed into the associated Azure VNET route table during the onboarding operation.

Impact:

Default route (0.0.0.0/0) is not installed in the onboarded Azure spoke VNET route table.
Traffic that depends on the default route, including traffic destined for the internet through an egress transit, for on-premises networks through an S2C-connected transit, or for another spoke, may not be routed correctly from the Azure VNET.

Workaround:

Manually add the default route to the Azure route table. Contact Aviatrix Support for assistance.

AVX-75452

In Azure environments, when Distributed Cloud Firewall (DCF) Security Group Orchestration attaches a Network Security Group (NSG) to a subnet, the subnet name is changed to all lowercase. Although Azure resource names are generally case-insensitive, this modification causes issues with Infrastructure as Code tools such as Terraform, which treat resource names as case-sensitive. Terraform may flag affected subnets for replacement, potentially disrupting existing deployments.

Impact:

Subnet names in Azure are modified to lowercase when Security Group Orchestration attaches NSGs
Terraform plans may show unexpected resource replacements for affected subnets
Customer naming conventions in the cloud may be altered without consent

Workaround:

In Terraform, add a lifecycle block with ignore_changes for subnet_id (as well as id in the azurerm_subnet resource) to prevent forced resource replacement. Note that this workaround does not restore the original subnet name casing.

AVX-75607

Gateway launch may fail with a tls: bad certificate error when pulling container images. The Controller’s registry TTL eviction (garbage collection) may fire while images are being downloaded to the gateway, corrupting in-flight blob transfers. The gateway’s container initialization cannot complete, and an internal identity-helper service on the gateway exits with code 125.

Impact:

Gateway creation fails with tls: bad certificate or unexpected EOF errors during container image pull
The gateway’s identity-helper service crash-loops with exit code 125
Manual intervention is required to recover

Workaround:

Restart the Controller’s core application service to reset the registry state, then retry gateway creation. Contact Aviatrix Support for assistance.

AVX-79012

Some gateways may become stuck in a failed configuration-push state for an extended period after an Image Upgrade to Aviatrix 10.0.0 (from 9.0.10). This has been observed primarily on lower-memory gateway instance types (for example, AWS t3.micro).

Impact:

Affected gateways may show a "Not Up-To-Date" config status and a down backup tunnel hours after the image upgrade completes. The root cause is a Distributed Cloud Firewall (DCF) configuration push failure caused by insufficient available memory on memory-constrained instance types.

Workaround:

Retry the gateway Image Upgrade. If the gateway remains stuck in this state, increase the gateway’s instance size for additional memory headroom, or contact Aviatrix Support.

AVX-79521

On Controller versions prior to 10.1.0, it is possible to onboard multiple Aviatrix access accounts that map to the same underlying cloud service provider (CSP) account. Because several Controller features assume a one-to-one relationship between an Aviatrix access account and a CSP account, duplicate access accounts can lead to unpredictable configuration and operational behavior. Duplicate is defined per CSP as follows:

AWS (including AWS GovCloud and AWS China): same account number, for both IAM role and access/secret key authentication.
Azure (including Azure Government and Azure China): same subscription.
GCP: same project.
OCI (including OCI Government): same tenancy and compartment combination.
Alibaba: same account number.

Starting in Controller 10.1.0, the Controller blocks new onboarding of duplicate access accounts across all supported CSPs. Existing duplicate access accounts continue to operate as-is and are not automatically removed.

Impact:

New duplicate access accounts can still be onboarded on Controller versions prior to 10.1.0.
Environments that already have duplicate access accounts may see inconsistent behavior in features that assume a unique CSP account per Aviatrix access account.

Workaround:

Onboard only one Aviatrix access account per underlying CSP account. If duplicate access accounts have already been onboarded and are causing issues, contact Aviatrix Support for assistance with identifying and removing the duplicates.

AVX-80977

A VPN user’s profile assignment could appear as N/A immediately after the user was attached to a profile through the API, until the user’s next reconnection.

Impact:

The user’s profile displays as N/A until the user’s next reconnection, even though the profile attachment succeeded.
This can cause confusion when auditing or verifying profile-based access policies shortly after attachment.

Workaround:

Have the affected user reconnect to update the displayed profile assignment. Contact Aviatrix Support for assistance.

AVX-81230

Enabling both Policy-Based Routing (PBR) and NAT logging under User VPN settings can cause high CPU utilization on the User VPN gateway during data-plane traffic. The high CPU usage occurs because NAT log entries generated by PBR are written to the gateway’s serial console.

Impact:

User VPN gateways with both PBR and NAT logging enabled may experience elevated CPU utilization while passing data-plane traffic, which can degrade VPN gateway performance.

Workaround:

Disable NAT logging on the affected User VPN gateway. If NAT logging must remain enabled, contact Aviatrix Support to apply a backend workaround.

AVX-81576

During a Gateway resize operation (for example, changing the Gateway’s underlying instance or VM size), the Gateway can experience a temporary period of traffic loss during the resize. This has been observed during testing on GCP, AWS, and Azure Gateways, where a resize between certain instance sizes produced approximately 2 minutes of packet loss.

Impact:

A Gateway resize can result in a brief traffic interruption, observed at approximately 2 minutes in testing.
This has been confirmed to occur on GCP, AWS, and Azure Gateways.

Workaround:

No workaround is currently available. A fix is planned for a future 10.1.x maintenance release.