[AutoPR- Security] Patch hdf5 for CVE-2026-26199, CVE-2026-26197 [MEDIUM]

[azurelinux-security]

Auto Patch hdf5 for CVE-2026-26199, CVE-2026-26197.

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

CVE-2026-26199 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1164704&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 hdf5 for CVE-2026-26199 (MEDIUM), CVE-2026-26197 (MEDIUM).

Change Log

• CVE-2026-26199
• CVE-2026-26197

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

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

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.

[v-sushilsati]

1. Both CVEs affect HDF5 1.14.6.
   CVE-2026-26199: listed as (affected range: <= 2.0.0)
   The vulnerable file (src/H5Odtype.c) and its associated logic are present in source.
   CVE-2026-26197: listed as (affected range: <= 2.0.0)
   All 12 vulnerable target files and affected logic are present.
   CVE-2026-26197 Backported: Yes
   CVE-2026-26199 Backported: Yes
2. AI CVE-2026-26197.patch matches with upstream patch. but missing Upstream-reference and also include [PATCH 3/3] section without commit.
   Because release_docs/CHANGELOG.md file is not exits. AI added metadata only.
3. Modified CVE-2026-26197.patch and added Upstream-reference and restructured CVE-2026-26197.patch into a single-patch format.
4. The initial AI CVE-2026-26199.patch was incomplete and only contained partial modifications for src/H5I.c.
   Updated the patch to include all necessary upstream code changes.
5. All upstream code changes are included for both CVEs. only release_docs/CHANGELOG.md was excluded because that file is not present in source tree.
6. Both patches have been applied successfully.

8. local build has passed.

[v-aaditya]

Buddy build has been triggered and it has passed.

[akhila-guruju]

Patch Analysis:

CVE-2026-26197:
Patch matches with the upstream patch. Changes for CHANGELOG.md are not included.

CVE-2026-26199:
Minor backport. Patch matches with the upstream patch. Slight variation around patched lines. Changes for CHANGELOG.md are not included.
The line herr_t status; /* Generic return value */ in test/links.c of upstream patch is not needed since it is not previously declared in azl source code.

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

Verdict: Patches LGTM.