[AutoPR- Security] Patch apr-util for CVE-2026-32327, CVE-2026-34502, CVE-2026-34501, CVE-2025-49506 [HIGH]

[Azure Linux Security Servicing Account (azurelinux-security)]

Auto Patch apr-util for CVE-2026-32327, CVE-2026-34502, CVE-2026-34501, CVE-2025-49506.

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

CVE-2026-32327 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1177462&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 apr-util for CVE-2026-32327 (MEDIUM), CVE-2026-34502 (HIGH), CVE-2026-34501 (HIGH), CVE-2025-49506 (HIGH).

Change Log

• CVE-2026-32327
• CVE-2026-34502
• CVE-2026-34501
• CVE-2025-49506

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-32327
• https://nvd.nist.gov/vuln/detail/CVE-2026-34502
• https://nvd.nist.gov/vuln/detail/CVE-2026-34501
• https://nvd.nist.gov/vuln/detail/CVE-2025-49506

Test Methodology

• Pipeline build id: Buddy Build URL
• 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.

[Ratiranjan5]

CVE-2026-32327:

• The apr-util package version 1.6.3 falls within the affected range (0 through 1.6.3, i.e. < 1.6.4) for CVE-2026-32327.
• Backported: YES
  • The AI patch has the upstream reference and its security logic is valid but the patch file itself was defective because every hunk was duplicated. The #define APR_XML_MAX_DEPTH 256, the depth field, the whole test_nesting_limit() function, the abts_run_test(...) line, and the CMakeLists.txt, all emitted twice which causing a redefinition compile error that breaks the %check stage.

• The AI patch and upstream patch both also used the uppercase macro APR_ASSERT_SUCCESS in test/testxml.c, which does not exist in 1.6.3. This version uses the lowercase apr_assert_success helper, so the build failed with undefined reference to APR_ASSERT_SUCCESS. I replaced it with apr_assert_success (matching the neighboring test_billion_laughs test).

• The upstream fix also relies on xml/apr_xml_internal.h, a file that does not exist in 1.6.3 (the parser struct is defined inline in xml/apr_xml.c). So the upstream patch cannot be applied as-is, that hunk is rejected. I folded the APR_XML_ERROR_DEPTH_LIMIT directly into apr_xml.c with no loss of functionality.

• The patch applies cleanly and has the upstream reference.

• the package builds successfully and the ptest/make check passes.

• Buddy Build has passed.