[AutoPR- Security] Patch libarchive for CVE-2026-16517 [LOW]

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

Auto Patch libarchive for CVE-2026-16517.

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

Change Log

• CVE-2026-16517

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

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

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.

[durgajagadeesh]

CVE-2026-16517:

1. The AI patch includes the upstream patch reference.
2. This CVE is affected because our source code(v3.7.7) falls below v3.8.8-3.1.hum1.
3. Backported: Yes
4. The AI patch matches the upstream patch reference, except for the archive_integer.h header file.
5. The upstream source code already includes archive_integer.h by default, but our source does not, so I added it manually.
6. Buddy build passes after adding this archive_integer.h file.
7. Buddy build passes.
8. Patch has been applied cleanly.

[Aditya Singh (v-aaditya)]

Peer-review -

1. AI patch matches with upstream patch but build failed as upstream patch is including archive_integer.h file which is not present in current source therefore the AI patch has been modified to include the .h file. Referred from upstream.
2. The patch applies cleanly.
3. The patch has upstream reference.
4. The ptest is getting passed.
5. The PR has security tag.
6. The latest Buddy Build has passed.

LGTM.

[Kanishk Bansal (Kanishk-Bansal)]

/azurepipelines run

[azure-pipelines]

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