Two deployments can run the same RabbitMQ version and expose very different attack paths. Start with the package release, then check which listeners, management views and authentication paths are actually in use.

What changed on November 22, 2026
Microsoft’s November 21 Security Update Guide revisions named 3.13.7-12 for four CVEs on the listed affected Azure Linux 3.0 package 3.13.7-11. On November 22, the production base repositories served 0:3.13.7-12.azl3 for x86-64 and ARM64. Both RPMs matched their repository SHA-256 checksums and name all four CVEs in their changelogs. Microsoft also lists 3.13.7-10 as affected for the two JOSE issues, and 3.13.7-9 and 3.13.7-10 for the management UI issue. The older rows have blank fix fields. This is a distro backport, and full older Azure Linux version bounds remain unspecified.
Where the fixes apply
CVE-2026-113431 can exhaust memory in a reachable HTTP/2 path that uses the affected Cowlib header decoder. Microsoft rates it Important without a numeric score in the reviewed row. The Erlang Ecosystem Foundation CNA rates it High, CVSS 4.0 8.7, and lists upstream Cowlib 2.7.0 through versions before 2.22.0. Verify which listeners and plugins actually use this path.
CVE-2026-66077 is stored cross-site scripting in the management UI. The RabbitMQ advisory requires TLS peer certificate verification, a certificate signed by a CA the broker trusts with an attacker-influenced subject, and an operator viewing the affected UI. Microsoft rates it Important, CVSS 3.1 6.1. RabbitMQ’s advisory rates it High, CVSS 4.0 7.3, and names upstream 3.13.15, 4.0.20, 4.1.11 and 4.2.6 as fixed on their respective branches.
CVE-2026-65631 affects untrusted RSA JWK parsing, with potential CPU exhaustion. CVE-2026-65632 affects ECDSA signature validation when the relevant JOSE verification path is used. Microsoft rates both Moderate without a numeric score in the reviewed rows. The upstream CNA rates them CVSS 4.0 6.9 and 5.1, respectively, and lists JOSE 1.11.13 as fixed. Check actual authentication and key-handling inputs before assigning exposure.
The same RPM changelog also mentions CVE-2026-67220. Microsoft previously mapped that JMS topic exchange issue from 3.13.7-9 to 3.13.7-10. The November 22 package check does not change that prior fix mapping.
CISA’s Known Exploited Vulnerabilities catalog does not list these CVEs as of November 22. Confirmed malicious exploitation, a federal KEV deadline and new vendor-directed incident-response or credential-rotation requirements were not verified.
What I would do across customer environments
Suggested MSP priority: High where untrusted HTTP/2 reaches the affected decoder or certificate identities can reach the affected management UI. Include affected key and signature processing in the same rollout.
- Inventory the full package release, broker nodes, enabled plugins, HTTP/2 reachability, management access, certificate issuance policies and JOSE consumers.
- Restrict unnecessary access to management and affected listener paths while awaiting patching. Preserve required broker traffic and keep peer certificate verification enabled.
- Pilot the supported Azure Linux 3.0 package and follow the existing broker maintenance procedure to upgrade and restart affected nodes. Update separately bundled and container-hosted copies through their own channels.
- Verify the running package, cluster and queue health, client connections, TLS authentication and management workflows. Track independently managed services separately.
Official sources
Last verified November 22, 2026 ET. Microsoft November CVRF · Microsoft October CVRF · Microsoft September CVRF · Cowlib CNA advisory · RabbitMQ advisory · JOSE JWK CNA advisory · JOSE ECDSA CNA advisory · Microsoft x86-64 repository metadata · Microsoft ARM64 repository metadata · CISA KEV catalog.