Whether you need an Azure container image rebuild depends on where your application’s .NET runtime lives. Microsoft said the built-in .NET 8, 9, and 10 images for Azure App Service on Linux had completed rollout on both the Latest and Standard channels by October 27, 2026. A self-contained deployment or custom container keeps its bundled runtime, so its owner must rebuild, test, and redeploy it with a patched runtime. Microsoft’s Azure App Service guidance covers that distinction and how to check the runtime an app is using.

First identify who supplies the runtime. A platform image update and a rebuild of your own bundled runtime are different fixes.

Identify which runtime your deployment uses

CVE-2026-111497 is an out-of-bounds write in the Brotli decoder. Microsoft says maliciously crafted compressed data can cause denial of service, information disclosure, or elevation of privilege. For .NET applications, the Azure App Service team identifies ASP.NET Core request decompression, automatic response decompression in HttpClient, and the Brotli APIs in System.IO.Compression as potentially affected paths. Automatic request and response decompression are not enabled by default, according to Microsoft; .NET Framework is not affected.

The distinction between a platform-managed runtime and a runtime packaged with your application determines the next step:

App Service for Linux deploymentWhat Microsoft’s platform update coversOperator action
Built-in .NET runtimeUpdated built-in .NET 8, 9, and 10 images on the Latest and Standard channelsCheck the runtime used by the running app and update application-managed dependencies where required.
Self-contained deploymentThe platform image update does not replace the runtime bundled with the deploymentRebuild with the applicable patched runtime, test, and redeploy.
Custom containerThe platform image update does not replace the runtime bundled in the containerRebuild the image with the applicable patched runtime, test, and redeploy.

Microsoft lists patched runtimes .NET 8.0.33, 9.0.22, and 10.0.14. The listed versions alone don’t establish which runtime a particular application process is using. Microsoft’s rollout statement applies to App Service on Linux, not App Service for Windows.

For broader context on the vulnerability, see NeoTeo’s earlier coverage of CVE-2026-111497.

Check the runtime your application is using

For an App Service Linux runtime check, Microsoft documents a sequence that starts with opening a shell in the running app and then listing installed shared runtimes. The list tells you what is installed; checking the application process tells you which runtime it actually uses.

  1. Open a shell in the running app. Microsoft’s guidance uses az webapp exec. The post describes this command as a preview feature and requires Azure CLI 2.90.0 or later for that workflow.
  2. List installed shared runtimes. Run dotnet --list-runtimes in the shell. This shows the shared runtimes installed in the environment, but not which one the application process uses.
  3. Check the application process. Use startup logging or diagnostics to verify the runtime used by the running app. dotnet --version reports the SDK version, not the runtime used by the application.
  4. Check scaled-out instances where applicable. Microsoft recommends verifying instances as needed, so the result covers the app’s running processes rather than just one environment check.

If the application bundles its runtime, use the rebuild, test, and redeployment path in the table; checking installed shared runtimes does not update that bundled copy.

Review container findings in Defender for Cloud

Microsoft Learn’s documented workflow requires Defender for Containers or Defender CSPM, along with a supported discovery and protection configuration. In the portal, open Recommendations, filter the resource type to Container, and open a recommendation to inspect its associated CVE, affected component, and fix-version details.

Those findings help identify affected components and fixes. The deployment owner still needs to apply the appropriate runtime update through the built-in platform or the customer-managed image, as applicable.