Upgrade gnutls to version 3.8.13 for CVE-2026-42012 and CVE-2026-42013

[Ratiranjan5]

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?

• Upgrade gnutls to version 3.8.13 for CVE-2026-42012 and CVE-2026-42013
• Upgrade dependency package nettle to version 3.10.
• In %check section, replaced the previous sed-based removal of test-ciphers-openssl.sh from Makefile.am with a cleaner skip mechanism (echo 'exit 77'). The old approach triggered automake 1.18 regeneration, but available one is of version 1.16.5. The new approach keeps the file present (satisfying make targets) while marking the test as SKIP per autotools convention.Added GNUTLS_SYSTEM_PRIORITY_FILE=/dev/null to prevent system crypto policy interference during test execution. Added automatic log dumping on test failure.
• Details about removed CVEs:
  Patch1: CVE-2024-28834.patch fixed in the version 3.8.4
  Patch2: CVE-2024-28835.patch fixed in the version 3.8.4
  Patch3: CVE-2024-12133.patch fixed in the version 3.8.9
  Patch4: CVE-2024-12243.patch fixed in the version 3.8.9
  Patch5: CVE-2025-32990.patch fixed in the version 3.8.10
  Patch6: CVE-2025-32989.patch fixed in the version 3.8.10
  Patch7: CVE-2025-32988.patch fixed in the version 3.8.10
  Patch8: CVE-2025-6395.patch fixed in the version 3.8.10
  Patch10: CVE-2025-9820.patch fixed in the version 3.8.11
  Patch11: CVE-2026-33845.patch fixed in the version 3.8.13

Change Log

• modified: SPECS/gnutls/gnutls.signatures.json
• modified: SPECS/gnutls/gnutls.spec
• modified: SPECS/nettle/nettle.signatures.json
• modified: SPECS/nettle/nettle.spec
• modified: cgmanifest.json

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

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

Test Methodology

• Local Build was sucessful.

• Patch Application:

[Kanishk-Bansal]

remove all patches from spec folder as well

[Ratiranjan5]

remove all patches from spec folder as well

Done.

[Ratiranjan5]

Buddy Build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1132411&view=results

[Ratiranjan5]

Buddy Build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1132411&view=results

Buddy build has passed.