Aviatrix Controller 10.1.20 Release Notes

Release Date: 27 October 2026

​

Corrected Issues in Aviatrix Release 10.1.20

This release installs the security patches for the following CVE advisories, detailed on the PSIRT Advisories page:

• CVE-2026-109618 and CVE-2026-109619 (PHP2Shell): remote code execution in PHP.
• CVE-2026-115560 (PHP session upload progress).
• CVE-2025-2171 and CVE-2025-2172: removal of the compromised eMudhra intermediate certificates from the Controller trust store.

​

Known Issues in Aviatrix Release 10.1.20

Issue	Description
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	Description: 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-81949	After a gateway software rollback, a small subset of HA gateways may incorrectly display the previous software version as the same value as the current software version, instead of the pre-rollback version. Impact: Affects the reported Previous Version on HA gateways after a Gateway Software Rollback. The rollback itself completes successfully and the gateway runs on the intended target version; only the version display is affected. Other gateways in the same rollback operation display the previous and current versions correctly. Workaround: No functional workaround is required. The rollback operation is successful despite the display discrepancy. Contact Aviatrix Support for assistance.