When a rebuild is required
Microsoft’s App Service team distinguishes three deployment models:
| Deployment | What to do |
|---|---|
| Built-in Linux.NET runtime | Verify the application process is using the patched platform runtime. |
| Self-contained application | Rebuild with the patched runtime, test, and redeploy. |
| Custom container | Rebuild the image with the patched runtime, test, and redeploy. |
The rollout covers built-in.NET 8, 9, and 10 images on both Latest and Standard channels. Switching channels is unnecessary, and this Linux rollout statement does not apply to App Service for Windows.
Microsoft’s security advisory identifies these patched runtime versions:
- .NET 8: 8.0.33
- .NET 9: 9.0.22
- .NET 10: 10.0.14.
What the Brotli vulnerability affects
CVE-2026-111497 is an out-of-bounds write in.NET’s Brotli decoder. Microsoft rates it High, with a CVSS 3.1 score of 8.1. Crafted compressed input could cause information disclosure, denial of service, or elevation of privilege.
Exposure requires processing attacker-controlled Brotli data through enabled ASP.NET Core request decompression, HttpClient automatic response decompression, or explicit System.IO.Compression Brotli APIs. Automatic request and response decompression are not enabled by default;.NET Framework is unaffected. An affected package’s presence alone does not establish exposure.
There is another rebuild trap: NativeAOT. Microsoft says updating a machine’s shared runtime cannot replace a decoder linked into an executable. Those applications need patched SDK/compiler or runtime-pack references, followed by republishing and redeployment. Direct references to affected packages also require updating.
Check the running app—not just the installed runtime
Microsoft documents this shell workflow using preview command az webapp exec, with Azure CLI 2.90.0 or later.
az webapp exec --resource-group <resource-group> --name <app-name>
Replace the placeholders with the target app’s values. Add --slot <slot-name> for a deployment slot or --instance <instance-id> to select an instance.
Inside the shell, run:
dotnet --list-runtimes
Then verify the application process through existing startup logging or diagnostics, inspecting System.Runtime.InteropServices.RuntimeInformation.FrameworkDescription. Check scaled-out instances too. Installed shared runtimes do not prove which runtime is active, and dotnet --version reports the SDK. Keep diagnostics private.
Find container CVEs in Defender for Cloud
Microsoft Learn’s running-container procedure concerns discovered Kubernetes workloads; it is not an App Service runtime-verification procedure. It requires Defender for Containers or Defender CSPM, plus either:
- Registry access with Kubernetes API access or Defender sensor.
- Agentless scanning for machines with Kubernetes API access or Defender sensor.
For covered workloads:
- Open Microsoft Defender for Cloud → Recommendations.
- Select Vulnerabilities, then Flat list.
- Choose Add filter → Resource type → Container → Apply.
- Open a recommendation and review its risk information and fix steps.
- Open Associated CVEs, then select a CVE to inspect severity, affected components, and fix version.
That coverage boundary matters. Because findings depend on discovery and protection components, an empty results list should not be treated as proof that an image is patched. This is an operational inference from Microsoft’s documented prerequisites—not a clean bill of health.
References
- Azure container image rebuild: when App Service needs one - NeoTeo NeoTeo · 2026-11-17T04:27:26+00:00
- .NET Brotli Security Updates on Azure App Service for Linux - Azure App Service azure.github.io
- View and Remediate Vulnerabilities for Running Containers - Microsoft Defender for Cloud | Microsoft Learn learn.microsoft.com