> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aviatrix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Aviatrix Controller 10.1.11 Release Notes

> Release Date: 19 October 2026

Release Date: 19 October 2026

## Corrected Issues in Aviatrix Release 10.1.11

<table>
  <thead><tr><th>Issue</th><th>Description</th></tr></thead>

  <tbody>
    <tr><td>AVX-82309</td><td>Fixed an issue where a gateway could continue enforcing a Distributed Cloud Firewall (DCF) SmartGroup's previous member list after a new address, such as a new Kubernetes pod IP, joined the SmartGroup, which could allow or deny traffic in a way that did not match the configured policy intent until state sync restarted.</td></tr>
  </tbody>
</table>

## Known Issues in Aviatrix Release 10.1.11

<table>
  <thead><tr><th>Issue</th><th>Description</th></tr></thead>

  <tbody>
    <tr><td>AVX-80977</td><td>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.<br /><br />**Impact:**<br /><br /><ul><li>The user's profile displays as N/A until the user's next reconnection, even though the profile attachment succeeded.</li><li>This can cause confusion when auditing or verifying profile-based access policies shortly after attachment.</li></ul>**Workaround:**<br /><br />Have the affected user reconnect to update the displayed profile assignment. Contact [Aviatrix Support](https://support.aviatrix.com/) for assistance.</td></tr>
    <tr><td>AVX-81230</td><td>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.<br /><br />**Impact:**<br /><br />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.<br /><br />**Workaround:**<br /><br />Disable NAT logging on the affected User VPN gateway. If NAT logging must remain enabled, contact [Aviatrix Support](https://support.aviatrix.com/) to apply a backend workaround.</td></tr>
    <tr><td>AVX-81576</td><td>**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.<br /><br />**Impact:**<ul><li>A Gateway resize can result in a brief traffic interruption, observed at approximately 2 minutes in testing.</li><li>This has been confirmed to occur on GCP, AWS, and Azure Gateways.</li></ul>**Workaround:**<br /><br />No workaround is currently available. A fix is planned for a future 10.1.x maintenance release.</td></tr>
    <tr><td>AVX-81949</td><td>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.<br /><br />**Impact:**<ul><li>Affects the reported **Previous Version** on HA gateways after a Gateway Software Rollback.</li><li>The rollback itself completes successfully and the gateway runs on the intended target version; only the version display is affected.</li><li>Other gateways in the same rollback operation display the previous and current versions correctly.</li></ul>**Workaround:**<br /><br />No functional workaround is required. The rollback operation is successful despite the display discrepancy. Contact [Aviatrix Support](https://support.aviatrix.com/) for assistance.</td></tr>
  </tbody>
</table>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.