[High] patch python-cryptography for CVE-2026-69249.

[AkarshHCL]

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

Vulnerability Summary

This PR fixes CVE-2026-69249, Duplicate self-signed intermediates can cause exponential path-building.

Backport adaptations for cryptography 42.0.5

1.Validation error API adaptation for cryptography 42.0.5

This adaptation is necessary because cryptography 42.0.5 uses the older error
model:

• ValidationError is an enum with a FatalError variant.
• It does not use the newer generic ValidationResult<'chain, T, B> type.
• Errors are constructed directly rather than through
  ValidationError::new(ValidationErrorKind::...).

2.Omission of the newer-API regression test.- Upstream patch had test too which was omitted as it was using newer apis not feasible to our version.

Change Log

• SPECS/python-cryptography/python-cryptography.spec
• SPECS/python-cryptography/CVE-2026-69249.patch

Does this affect the toolchain?

NO

Links to CVEs

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

Test Methodology

Screenshot of successful local build-

patch is getting applied cleanly-

Done the advisory Poc to check vulnerability is fixed or not poc reference link-GHSA-jwv3-5hgf-82ww
Before fix output-

After fix-

• Pipeline build url:
  https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1179507&view=results

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.