[AUTO-CHERRYPICK] Upgrade thrift to 0.24.0 for CVE-2026-48144, CVE-2026-49158, CVE-2026-58023, CVE-2026-58662, CVE-2026-66053, CVE-2026-55970, CVE-2026-41608, CVE-2026-55969, CVE-2026-43871, CVE-2026-48586, CVE-2026-48145, CVE-2026-55971, CVE-2026-41606, CVE-2026-41607 - branch 3.0-dev - #18279
[AUTO-CHERRYPICK] Upgrade thrift to 0.24.0 for CVE-2026-48144, CVE-2026-49158, CVE-2026-58023, CVE-2026-58662, CVE-2026-66053, CVE-2026-55970, CVE-2026-41608, CVE-2026-55969, CVE-2026-43871, CVE-2026-48586, CVE-2026-48145, CVE-2026-55971, CVE-2026-41606, CVE-2026-41607 - branch 3.0-dev#18279azurelinux-ci-jwt-app[bot] wants to merge 1 commit into
Conversation
…-58023, CVE-2026-58662, CVE-2026-66053, CVE-2026-55970, CVE-2026-41608, CVE-2026-55969, CVE-2026-43871, CVE-2026-48586, CVE-2026-48145, CVE-2026-55971, CVE-2026-41606, CVE-2026-41607 (#18239) (cherry picked from commit 66b5939)
Auto Cherry-Pick SPEC Validation Summary
|
| Source (fasttrack) | Target (3.0-dev) | Resolved | |
|---|---|---|---|
| Version | 0.24.0 | 0.15.0 | 0.24.0 |
| Release | 1 | 6 | 1 |
| Patches | 1 | 6 | 1 |
| Conflict | No |
- Version-release 0.24.0-1 is not higher than Source 0.24.0-1
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
|
@azurelinux-ci-jwt-app[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
1 similar comment
|
@azurelinux-ci-jwt-app[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
This is an auto-generated pull request to cherry-pick commit 66b5939 to 3.0-dev. Original PR: #18239
In case of no merge conflicts, the PR is merged without approval because it's an automated cherry-pick of an already approved PR.
In case of merge conflicts, an AI-based conflict resolver will attempt to resolve conflicts and might make mistakes. The reviewer must check AI's work before approving.