[AutoPR- Security] Patch erlang for CVE-2026-59251, CVE-2026-58227, CVE-2026-55953, CVE-2026-55737, CVE-2026-42792 [HIGH]

[azurelinux-security]

Auto Patch erlang for CVE-2026-59251, CVE-2026-58227, CVE-2026-55953, CVE-2026-55737, CVE-2026-42792.

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

CVE-2026-59251 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1172088&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 erlang for CVE-2026-59251 (HIGH), CVE-2026-58227 (HIGH), CVE-2026-55953 (HIGH), CVE-2026-55737 (MEDIUM), CVE-2026-42792 (MEDIUM).

Change Log

• CVE-2026-59251
• CVE-2026-58227
• CVE-2026-55953
• CVE-2026-55737
• CVE-2026-42792

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-59251
• https://nvd.nist.gov/vuln/detail/CVE-2026-58227
• https://nvd.nist.gov/vuln/detail/CVE-2026-55953
• https://nvd.nist.gov/vuln/detail/CVE-2026-55737
• https://nvd.nist.gov/vuln/detail/CVE-2026-42792

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.

[Ratiranjan5]

Patch Analysis:

CVE-2026-42792:

• The erlang package version 26.2.5.21 falls within the affected range for CVE-2026-42792 (all versions prior to 27.3.4.15). - Backported: No (AI patch is fine).
  • The patch aligns with the upstream, all hunks applied cleanly, and the affected code is present (erts/epmd/src/epmd_srv.c — do_accept EMFILE/ENFILE handling).

CVE-2026-55737:

• The erlang package version 26.2.5.21 falls within the affected range for CVE-2026-55737 (all versions prior to 27.3.4.15). - Backported: No (AI patch is fine).
  • The patch aligns with the upstream, all hunks applied cleanly, and the affected code is present (erts/emulator/beam/external.c — large-tuple size guard).

CVE-2026-55953:

• The erlang package version 26.2.5.21 falls within the affected range for CVE-2026-55953 (all versions prior to 27.3.4.15).
• Backported: No (AI patch is fine).
• The patch aligns with the upstream, all hunks applied cleanly, and the affected code is present (lib/ssl/src/ssl_handshake.erl — client cipher-suite membership check).

CVE-2026-58227:

• The erlang package version 26.2.5.21 falls within the affected range for CVE-2026-58227 (all versions prior to 27.3.4.15).
• Backported: No (AI patch is fine).
• The patch aligns with the upstream, all hunks applied cleanly, and the affected code is present (lib/ssl/src/ssl_certificate.erl — acyclic digraph chain building + MAX_CHAIN cap; includes tests).

CVE-2026-59251:

• The erlang package version 26.2.5.21 falls within the affected range for CVE-2026-59251 (all versions prior to 27.3.4.15).

• Backported: YES — the AI patch was incomplete and would not compile.

  • The AI-generated patch updated the helper functions to pass around the new policy_tree_node_count (used to cap policy-tree growth and prevent a DoS), but it forgot to update the code that calls them. This left the function signatures mismatched, so the module wouldn't compile and the node-count limit wasn't enforced.
  • Aligning with the upstream fix, I added the missing caller-side changes in pubkey_cert.erl:
    • validate_extensions: capture {Tree, NodeCount} from process_policy_tree and store the count.
    • handle_last_cert: read the count and call the new 3-arg policy_tree_intersection.
    • handle_policy_mappings and handle_policy_mapping: thread NodeCount through the chain, return {tree, Tree, NodeCount}, and add the assert_policy_tree_node_count check that actually enforces the cap.

• upstream renamed the variable OtpCert → Cert, whereas this backport retains OtpCert to match the existing source code.

• The all 5 AI patch includes upstream patch reference.

• The local build and buddy build has passed.
  Link: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1172585&view=results

• The patches apply cleanly. (Checked .rpm.log)

• The SPEC file has been updated to include - bumped up release number, patch file and changelog history.