[AutoPR- Security] Patch libxslt for CVE-2025-11731 [LOW]

[azurelinux-security]

Auto Patch libxslt for CVE-2025-11731.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=987595&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 libxslt for CVE-2025-11731 (LOW).

Change Log

• CVE-2025-11731

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2025-11731

Test Methodology

• Pipeline build id: Buddy Build URL

[Kanishk-Bansal]

Patch Analysis (the patch applies cleanly)

• Buddy Build 
• patch applied during the build (check rpm.log)
• patch include an upstream reference
• PR has security tag

[Kanishk-Bansal]

Full Build

[kgodara912]

Full build has failures due to timeout duration of build, 24 hours. Re-triggered it.

[Kanishk-Bansal]

Re-triggered the failing golden container tests

[AkarshHCL]

Re-triggered the failing golden container tests

HI @kgodara912 after retrigger of full-build this error is thrown is this because it even didn't retriggered as golden container tests as been once already triggered?

[Kanishk-Bansal]

re full build

[kgodara912]

Full build is successful except long failing container test failures which are failing from some time. Patch matches with upstream reference. LGTM.