[AutoPR- Security] Patch jq for CVE-2026-43896, CVE-2026-43895, CVE-2026-41257, CVE-2026-41256, CVE-2026-40612, CVE-2026-44777 [MEDIUM]

[azurelinux-security]

Auto Patch jq for CVE-2026-43896, CVE-2026-43895, CVE-2026-41257, CVE-2026-41256, CVE-2026-40612, CVE-2026-44777.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1116141&view=results
Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1116950&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-43896 (MEDIUM), CVE-2026-43895 (MEDIUM), CVE-2026-41257 (MEDIUM), CVE-2026-41256 (MEDIUM), CVE-2026-40612 (MEDIUM), CVE-2026-44777 (MEDIUM).

Change Log

• CVE-2026-43896
• CVE-2026-43895
• CVE-2026-41257
• CVE-2026-41256
• CVE-2026-40612
• CVE-2026-44777

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-43896
• https://nvd.nist.gov/vuln/detail/CVE-2026-43895
• https://nvd.nist.gov/vuln/detail/CVE-2026-41257
• https://nvd.nist.gov/vuln/detail/CVE-2026-41256
• https://nvd.nist.gov/vuln/detail/CVE-2026-40612
• https://nvd.nist.gov/vuln/detail/CVE-2026-44777

Test Methodology

• Pipeline build id: Buddy Build URL
• Pipeline build id: Buddy Build URL

[akhila-guruju]

Analysis:
CVE-2026-40612:
Minor modification done. Added extra closed brackets () after try in jq.test file to avoid syntax errors caused due to version differences.

time="2026-05-13T06:30:40Z" level=debug msg="Test #453:jq: error: syntax error, unexpected as (Unix shell quoting issues?) at <top-level>, line 1:"
time="2026-05-13T06:30:40Z" level=debug msg="try (reduce range(10001) as $_ ([]; [.]) as $x | $x | contains($x)) catch .                                         "
time="2026-05-13T06:30:40Z" level=debug msg="jq: 1 compile error"
time="2026-05-13T06:30:40Z" level=debug msg=" 'try [\"ok\", setpath([1]; 1)] catch [\"ko\", .]' at line number 2142"

CVE-2026-41256:
AI patch Matches with upstream patch.

CVE-2026-41257:
AI patch Matches with upstream patch.

CVE-2026-43896:
Added extra closed brackets () after try in jq.test file to avoid syntax errors caused due to version differences.

time="2026-05-13T09:03:13Z" level=debug msg="Test #453:jq: error: syntax error, unexpected as, expecting end of file (Unix shell quoting issues?) at <top-level>, line 1:"
time="2026-05-13T09:03:13Z" level=debug msg="reduce range(10000) as $_ ({}; {a: .}) as $x | $x * $x | length                                       "
time="2026-05-13T09:03:13Z" level=debug msg="jq: 1 compile error"
time="2026-05-13T09:03:13Z" level=debug msg="jq: error: syntax error, unexpected as (Unix shell quoting issues?) at <top-level>, line 1:"
time="2026-05-13T09:03:13Z" level=debug msg="try (reduce range(10001) as $_ ({}; {a: .}) as $x | $x * $x) catch .                                            "
time="2026-05-13T09:03:13Z" level=debug msg="jq: 1 compile error"
time="2026-05-13T09:03:13Z" level=debug msg=" 'try [\"ok\", setpath([1]; 1)] catch [\"ko\", .]' at line number 2142"
time="2026-05-13T09:03:13Z" level=debug msg="Test #457: 'try ((reduce range(10001) as $_ ([]; [.])) as $x | $x | contains($x)) catch .' at line number 2164"
time="2026-05-13T09:03:13Z" level=debug msg="Test #458: 'reduce range(10000) as $_ ({}; {a: .}) as $x | $x * $x | length' at line number 2169"
time="2026-05-13T09:03:13Z" level=debug msg="*** Test program failed to compile at line 2169: reduce range(10000) as $_ ({}; {a: .}) as $x | $x * $x | length"
time="2026-05-13T09:03:13Z" level=debug msg="Test #459: 'try (reduce range(10001) as $_ ({}; {a: .}) as $x | $x * $x) catch .' at line number 2173"
time="2026-05-13T09:03:13Z" level=debug msg="*** Test program failed to compile at line 2173: try (reduce range(10001) as $_ ({}; {a: .}) as $x | $x * $x) catch ."
time="2026-05-13T09:03:13Z" level=debug msg="457 of 459 tests passed (2 malformed, 0 skipped)"
time="2026-05-13T09:03:13Z" level=debug msg="FAIL tests/jqtest (exit status: 1)"

[akhila-guruju]

CVE-2026-43896:
Excluded patching for the file src/parse.c. Since parser.c is a autogenerated C code, cannot be patched manually. So, generated it by using --enable-maintainer-mode configure option in spec file. Makefile.am
Rest all changes matches with upstream.

CVE-2026-44777:
Patch matches with upstream patch. Slight variation in deleted lines