[AutoPR- Security] Patch jq for CVE-2026-49839, CVE-2026-47770 [HIGH]

[azurelinux-security]

Auto Patch jq for CVE-2026-49839, CVE-2026-47770.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1147854&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 jq for CVE-2026-49839 (HIGH), CVE-2026-47770 (MEDIUM).

Change Log

• CVE-2026-49839
• CVE-2026-47770

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

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

Test Methodology

• Pipeline build id: Buddy Build URL

[v-aaditya]

Updated patch for CVE-2026-47770 -

1. The CVE affects the package jq as it has version 1.7.1 which is in affected range < 1.8.2.
2. The Patch matches with upstream patch except few minor changes have been done in all 3 source files except test file.
3. Local build is successful and patch applies cleanly. (Checked .rpm.log)
4. pTest is getting passed.
5. Patch has upstream patch reference.
6. Buddy build is triggered and it has passed.