Upgrade azurelinux-image-tools to version 1.3.0

[v-aaditya]

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

• Upgrade azurelinux-image-tools to version 1.3.0.
• The azurelinux-image-tools package has been upgraded to version 1.3.0 and the CVE-2026-27141, CVE-2026-29181 and CVE-2026-39882 does not affect the respective vendor packages as they are not in affected range. Please refer below screenshot -
  

Change Log

• deleted: SPECS/azurelinux-image-tools/CVE-2026-27141.patch
• modified: SPECS/azurelinux-image-tools/azurelinux-image-tools.signatures.json
• modified: SPECS/azurelinux-image-tools/azurelinux-image-tools.spec
• modified: cgmanifest.json

Does this affect the toolchain?

NO

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-27141
• https://nvd.nist.gov/vuln/detail/CVE-2026-29181
• https://nvd.nist.gov/vuln/detail/CVE-2026-39882

Test Methodology

• Local Build was sucessful.
  

• The license script shows no warning.

• The changelog history has been verified using rpmspec command and there are no issues in it.

• The Installation and Uninstallation of generated RPMs could not be verified on docker image due to some issue in updating AzureLinux repo.