Azure Linux 4.0 has a backported Starlette fix

Conceptual illustration of a web request passing through an inspection checkpoint and branching toward cloud servers.

If an Azure Linux 4.0 app uses Starlette, check what the running image actually imports. Microsoft backported a fix, and the upstream and RPM version numbers look different.

New November 16, 2026 at 22:59 UTC. MSRC added Azure Linux 4.0 package guidance for CVE-2026-48710 (upstream GHSA-86qp-5c8j-p5mr). The Starlette maintainers originally published their advisory May 21, 2026. Last verified November 17, 2026.

Who should check

Upstream Starlette through 1.0.0 is affected when application code or middleware uses request.url or request.url.path for security decisions and the service receives a malformed Host header. An upstream proxy only mitigates this path if it rejects or normalizes malformed Host values and the application does not trust attacker-controlled forwarded host headers. MSRC lists a fixed Azure Linux 4.0 build and provides no separate affected RPM range. Check Azure Linux 4.0 workloads that actually load Starlette, including containers and Python virtual environments.

Fixed package and rollout

For Microsoft’s RPM, MSRC lists 0:0.52.1-6.azl4. The Microsoft spec records the backport and the production build-dependency repositories list python3-starlette-0.52.1-6.azl4.noarch.rpm for x86_64 and aarch64. Verify availability in the repository configured for each workload. For pip-managed Starlette, the upstream fix is 1.0.1. A system RPM update leaves a separate pip installation or container layer untouched.

Microsoft rates its package Moderate, CVSS 3.1 6.5. CISA added CVE-2026-48710 to KEV on September 2, with a September 16 federal remediation deadline. Microsoft’s package entry provides no Azure-Linux-specific exploitation or credential rotation guidance.

Suggested MSP priority is urgent for exposed apps with path-based access controls. Inventory the imported Starlette package, image or environment, and the proxy and application authorization configuration. Restrict exposure or enforce Host validation at the edge while you patch. Rebuild and redeploy affected images or update the package through its approved channel. Verify the imported runtime version and that protected routes still reject unauthorized access.

MSRC CVRF package entry · Microsoft backport spec · Microsoft x86_64 repository metadata · Microsoft aarch64 repository metadata · Starlette advisory · CISA KEV.

Share this article