[AutoPR- Security] Patch rabbitmq-server for CVE-2026-57221, CVE-2026-57220, CVE-2026-57219, CVE-2026-57218, CVE-2026-57217, CVE-2026-57215, CVE-2026-57214, CVE-2026-57213, CVE-2026-57212, CVE-2026-57211 [HIGH]

[azurelinux-security]

Auto Patch rabbitmq-server for CVE-2026-57221, CVE-2026-57220, CVE-2026-57219, CVE-2026-57218, CVE-2026-57217, CVE-2026-57215, CVE-2026-57214, CVE-2026-57213, CVE-2026-57212, CVE-2026-57211.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1160673&view=results

CVE-2026-57221 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1160680&view=results
CVE-2026-57220 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1160679&view=results
CVE-2026-57219 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1160681&view=results
CVE-2026-57218 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1160682&view=results
CVE-2026-57215 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1160683&view=results
CVE-2026-57212 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1160684&view=results

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?

• Auto Patch rabbitmq-server for CVE-2026-57221 (MEDIUM), CVE-2026-57220 (HIGH), CVE-2026-57219 (HIGH), CVE-2026-57218 (MEDIUM), CVE-2026-57217 (HIGH), CVE-2026-57215 (HIGH), CVE-2026-57214 (HIGH), CVE-2026-57213 (MEDIUM), CVE-2026-57212 (HIGH), CVE-2026-57211 (MEDIUM).

Change Log

• CVE-2026-57221
• CVE-2026-57220
• CVE-2026-57219
• CVE-2026-57218
• CVE-2026-57217
• CVE-2026-57215
• CVE-2026-57214
• CVE-2026-57213
• CVE-2026-57212
• CVE-2026-57211

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-57221
• https://nvd.nist.gov/vuln/detail/CVE-2026-57220
• https://nvd.nist.gov/vuln/detail/CVE-2026-57219
• https://nvd.nist.gov/vuln/detail/CVE-2026-57218
• https://nvd.nist.gov/vuln/detail/CVE-2026-57217
• https://nvd.nist.gov/vuln/detail/CVE-2026-57215
• https://nvd.nist.gov/vuln/detail/CVE-2026-57214
• https://nvd.nist.gov/vuln/detail/CVE-2026-57213
• https://nvd.nist.gov/vuln/detail/CVE-2026-57212
• https://nvd.nist.gov/vuln/detail/CVE-2026-57211

Test Methodology

• Pipeline build id: Buddy Build URL

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[v-sushilsati]

1. Upstream commit references in all patches are correct.
2. All patches match their respective upstream implementations. except changes in some source file and test files in respective CVE are not included as these files do not exist.
3. CVE-2026-57211, CVE-2026-57214, CVE-2026-57218: The three CVEs mentioned do not affect version 3.13.7 according to NVD. However, applying them is safe since the affected code is present in this branch.
4. CVE-2026-57212: A build failure occurred because CVE-2026-57212.patch referenced a missing LOG_WARNING module/macro in rabbit_mgmt_util.erl because does not include logging macro headers, This was resolved by using the existing API, rabbit_log:warning(...).
5. CVE-2026-57218: A build failure was also caused by CVE-2026-57218.patch due to undefined functions: recheck_consumers/1 and server_consumer_cancel_supported/1. These were resolved by backporting both functions from upstream.
For CVE-2026-57218, the recheck cancellation path was updated to use the branch-native rabbit_queue_type:cancel(Q, CTag, undefined, Username, QStates0) (cancel/5) instead of the newer cancel/3 function from upstream.
6. CVE-2026-57215: The upstream fix for CVE-2026-57215 relies on the rabbit_volatile_queue:is/1 module, which does not exist in this branch. A safer workaround for 3.13.7 was implemented by avoiding the introduction of that module and instead leveraging the existing direct-reply-to prefix logic already present in rabbit_exchange.erl. Also confirm the changes with test please refer to the Test section:
7. CVE-2026-57216: is also fixed in same PR.
8. local build and buddy build are ok.
Buddy build Pipelines - Run PR-18025+rabbitmq-server+unknown

Test Section:
CVE-2026-57215: I have installed the rabbitmq-server-3.13.7-7.azl3.x86_64.rpm in docker container.
And create and run the python test with following three test scenario and result are as per CVE-2026-57215 fix.

Output with including patch CVE-2026-57215 fix(rabbitmq-server-3.13.7-7.azl3.x86_64.rpm)

Output with rabbitmq-server-3.13.7-6.azl3.x86_64.rpm (without patch)

[v-aaditya]

Buddy Build has been triggered and it has passed !