An authentication module can be present on a server without every application using it. For Azure Linux 4.0 environments that do use Apache’s mod_auth_openidc, Microsoft now provides a concrete distribution fix mapping for CVE-2026-54789. Check the running module and the authentication path before closing the ticket.

What changed
Microsoft’s August CVRF record, revision 2.0 dated November 20, 2026 at 01:10:11 UTC (November 19 at 8:10 p.m. ET), maps Azure Linux 4.0 mod_auth_openidc 2.4.19.2-5.azl4 to fixed build 0:2.4.19.4-6.azl4. This is a newly verified distribution remediation mapping; the upstream advisory and upstream fix are older. The original Microsoft publication was November 16, 2026 at 22:56:48 UTC.
The exact fixed package is listed in Microsoft’s production base repositories for x86_64 and aarch64. Both repository metadata checksums were verified and both exact RPM URLs responded successfully on November 20. The files were already hosted on November 18; this is not a claim that new binaries were released today or installed in any customer environment.
Applicability and impact
The vendor describes mod_auth_openidc as an OpenID Connect authentication and authorization module for Apache 2.x. Upstream versions before 2.4.19.4 are affected. Microsoft explicitly lists Azure Linux 4.0 package 2.4.19.2-5.azl4; complete distribution-specific older-version bounds and backport status were not supplied in that row. Do not automatically apply this package mapping to other operating systems, appliances, bundled copies or container images.
A malformed Cookie header containing a token beginning with the configured state-cookie prefix (default mod_auth_openidc_state_) but no equals sign can cause an out-of-bounds read and a one-byte out-of-bounds NUL write. The parser runs before session or state validation on requests starting an authentication flow and on the OIDCRedirectURI callback. An unauthenticated remote client can reach the issue where those vulnerable module paths are exposed.
The vendor describes a worker crash and remotely triggerable denial of service, plus limited memory corruption. The bytes read are not returned to the client. This finding does not establish credential theft, an identity-provider compromise or remote code execution. It is not a vulnerability claim against Entra ID itself.
Microsoft rates the Azure Linux mapping Important, CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). The upstream vendor advisory rates it High with the same CVSS 3.1 score and vector. Suggested MSP priority: High when an affected module handles reachable authentication traffic.
Exploitation and temporary controls
CVE-2026-54789 was absent from the full CISA KEV catalog checked November 20. Confirmed malicious exploitation was not verified, and there is no KEV federal remediation deadline for this CVE. A public technical description is not proof of exploitation.
The vendor states that no in-product workaround is available. As a temporary exposure reduction, an upstream reverse proxy or WAF can reject or normalize malformed Cookie headers containing tokens without an equals sign. That control has limits: validate the actual request path and legitimate authentication behavior, and do not treat it as a substitute for upgrading.
MSP action sequence
Inventory: Identify the actual OS, complete package release, Apache module configuration, authentication entry points, callback exposure and all container or bundled copies. Package presence alone does not establish that the vulnerable parser is reachable.
Contain where warranted: Limit unnecessary access to affected authentication paths and evaluate the vendor’s temporary proxy/WAF control without breaking required sign-in flows. Preserve evidence and use the normal incident-response process if suspicious activity is found; no blanket credential-rotation instruction was verified for this advisory.
Patch: Pilot the supported Azure Linux distribution update to 2.4.19.4-6.azl4 or a vendor-supported superseding build. For other distributions, use their maintained fix guidance; upstream’s fixed version is 2.4.19.4.
Verify: Restart or redeploy affected Apache consumers as appropriate, confirm the fixed module is loaded, test legitimate sign-in and callback flows, and safely validate malformed-header rejection and worker stability. Updating a host package does not update a separate container or prove that every worker loaded the fix.
Official sources and verification
Microsoft August CVRF · MSRC CVE-2026-54789 · OpenIDC vendor advisory GHSA-vgr5-qcpp-x2pr · Vendor-authored CNA record.
Microsoft x86_64 production metadata · Microsoft aarch64 production metadata · Azure Linux upgrade guidance · CISA KEV.
Last verified November 20, 2026. Status: patch available; applicability requires validation. Other pending advisory reviews and source-access gaps remain open. No customer product use or exposure is assumed.