Skip to content

[Medium] Patch packer for CVE-2026-45570 and CVE-2026-45571#17905

Open
v-aaditya wants to merge 1 commit into
microsoft:3.0-devfrom
Kanishk-Bansal:topic-cve-fix/3.0/packer-1.9.5/CVE-2026-45571
Open

[Medium] Patch packer for CVE-2026-45570 and CVE-2026-45571#17905
v-aaditya wants to merge 1 commit into
microsoft:3.0-devfrom
Kanishk-Bansal:topic-cve-fix/3.0/packer-1.9.5/CVE-2026-45571

Conversation

@v-aaditya

@v-aaditya v-aaditya commented Jul 3, 2026

Copy link
Copy Markdown
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
Change Log
Does this affect the toolchain?

NO

Links to CVEs
Test Methodology
  • Local build was successful.
  • Patch applies cleanly
  • License check script shows no warning.
  • Installation and Uninstallation on docker image was successful.

@microsoft-github-policy-service microsoft-github-policy-service Bot added Packaging 3.0-dev PRs Destined for AzureLinux 3.0 labels Jul 3, 2026
@v-aaditya

Copy link
Copy Markdown
Author

Vendor tarball needs to be uploaded on blobstore once review is completed.

@v-aaditya v-aaditya marked this pull request as ready for review July 3, 2026 11:10
@v-aaditya v-aaditya requested a review from a team as a code owner July 3, 2026 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.0-dev PRs Destined for AzureLinux 3.0 Packaging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant