[AutoPR- Security] Patch libxml2 for CVE-2026-0992, CVE-2026-0990, CVE-2025-7425 [HIGH]

[azurelinux-security]

Auto Patch libxml2 for CVE-2026-0992, CVE-2026-0990, CVE-2025-7425.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1036410&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 libxml2 for CVE-2026-0992 (LOW), CVE-2026-0990 (MEDIUM), CVE-2025-7425 (HIGH).

Change Log

• CVE-2026-0992
• CVE-2026-0990
• CVE-2025-7425

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-0992
• https://nvd.nist.gov/vuln/detail/CVE-2026-0990
• https://nvd.nist.gov/vuln/detail/CVE-2025-7425

Test Methodology

• Pipeline build id: Buddy Build URL

[akhila-guruju]

Patch libxml2 for CVE-2025-7425
This is a mitigation patch. While the issue is underlying in libxslt (and the CVE assigned for it), a
mitigation can be implemented in src:libxml2.
AI backport patch was good. The patch for v2.11.5 of libxml2 in 3.0 can be applied for v2.10.4 of libxml2 in 2.0 [PR in 3.0 #15479]

Backported for CVE-2026-0992 to fix build
func xmlCatalogPrintDebug() definition has been added in catalog.c file which was used in the CVE fix and xmlVPrintErrorMessage() func definition added in error.c which is used inside xmlCatalogPrintDebug() func.

xmlCatalogPrintDebug() - https://gitlab.gnome.org/GNOME/libxml2/-/blob/master/catalog.c?ref_type=heads#L237
xmlVPrintErrorMessage() - https://gitlab.gnome.org/GNOME/libxml2/-/blob/master/error.c?ref_type=heads#L1345

[Kanishk-Bansal]

Buddy Build

[Kanishk-Bansal]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jslobodzian]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[CBL-Mariner-Bot]

Auto cherry-pick results:

• main ✅ -> [AUTO-CHERRYPICK] [AutoPR- Security] Patch libxml2 for CVE-2026-0992, CVE-2026-0990, CVE-2025-7425 [HIGH] - branch main #15626

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1038865&view=results