[AutoPR- Security] Patch rest for CVE-2026-16615 [MEDIUM]

[azurelinux-security]

Auto Patch rest for CVE-2026-16615.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1168500&view=results

CVE-2026-16615 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1168503&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 rest for CVE-2026-16615 (MEDIUM).

Change Log

• CVE-2026-16615

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

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

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.

[v-swapsahu]

Patch Analysis:

Backported: Yes
The patch aligns with the upstream fix, with only minor backport adaptation.

• fixes a pre-existing typo (con.set_quoted → conf.set_quoted). Already fixed in https://gitlab.gnome.org/GNOME/librest/-/merge_requests/44.patch .

Fix Summary
CVE-2026-16615 is addressed by replacing the insecure GRand-based random string generator with a cryptographically secure one, across three files:

Spec File Change
rest.spec: Changes %autosetup to %autosetup -p1 to fix patch application failure in %prep .

Backport completeness
I do not see any missing upstream backport work in this AutoPR.

[akhila-guruju]

Patch Analysis:
Backported: Yes
AI patch matches with upstream patch. Slight variation around some of the patched lines. Patch fixes weak random number generation in PKCE implementation by replacing the insecure GRand/g_rand_* PRNG with a cryptographically secure random source

Additional upstream build fix typo also fixed in this patch.
Ref: https://gitlab.gnome.org/GNOME/librest/-/commit/10fdf11d7d109f6b37ef9cff475a6be6fe76fd20

• Buddy Build
• patch applied during the build (check rpm.log)
• patch include an upstream reference
• PR has security tag

Verdict: AI patch LGTM.