[AutoPR- Security] Patch expat for CVE-2026-24515 [LOW]

[azurelinux-security]

Auto Patch expat for CVE-2026-24515.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1036427&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 expat for CVE-2026-24515 (LOW).

Change Log

• CVE-2026-24515

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-24515

Test Methodology

• Pipeline build id: Buddy Build URL

[v-aaditya]

AI Patch Analysis:

Upstream Patch reference - https://github.com/libexpat/libexpat/commit/f14b08452fd7f5d95428716a72d54918196ccf7c.patch

1. The AI patch matches with the upstream patch, also it has not included the changes made in "expat/Changes" file, since it is not present in our version.
2. Upstream patch reference is not present in AI patch file, neither in Summary section of PR.
3. The AI patch actually has 3 patch headers, just like upstream patch, but in upstream patch the 3rd header was for changes in file "expat/Changes", since this file is not present in our version, the AI patch has the 3rd header, but it is empty. So, this can be removed.
4. Buddy Build is successful, checked the build log and the patch has been applied cleanly.