[AutoPR- Security] Patch expat for CVE-2026-76957, CVE-2026-76956, CVE-2026-76641, CVE-2026-66046 [HIGH]

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

Auto Patch expat for CVE-2026-76957, CVE-2026-76956, CVE-2026-76641, CVE-2026-66046.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1186945&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-76957 (MEDIUM), CVE-2026-76956 (MEDIUM), CVE-2026-76641 (HIGH), CVE-2026-66046 (HIGH).

Change Log

• CVE-2026-76957
• CVE-2026-76956
• CVE-2026-76641
• CVE-2026-66046

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-76957
• https://nvd.nist.gov/vuln/detail/CVE-2026-76956
• https://nvd.nist.gov/vuln/detail/CVE-2026-76641
• https://nvd.nist.gov/vuln/detail/CVE-2026-66046

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.

[kgodara912]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.

[kgodara912]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.

[kgodara912]

There will be an expat release 2.8.4 soon (as per expat homepage, ETA is 31st August 2026) but that is little far for CVE timelines, hence raising patches.

[kgodara912]

All the patches are clean patch applications except one which has ONLY changelog file changes removed which are unrelated to CVE; buddy build is successful. PR check build and test phases are successful. Circular dependency failure is on the updated expat rpms itself. LGTM.