[AUTO-CHERRYPICK] [HIGH] Patch kata-containers-cc for CVE-2025-5791 and CVE-2025-4574 - branch 3.0-dev - #17772
Merged
CBL-Mariner-Bot merged 1 commit intoJun 19, 2026
Conversation
CBL-Mariner-Bot
added
the
Auto Fast-track Cherry-pick
Collaborator
Author
Auto Cherry-Pick SPEC Validation Summary
|
| Source (fasttrack) | Target (3.0-dev) | Resolved | |
|---|---|---|---|
| Version | 3.15.0.aks0 | 3.15.0.aks0 | 3.15.0.aks0 |
| Release | 14 | 13 | 14 |
| Patches | 6 | 4 | 6 |
| Conflict | No |
- Version-release 3.15.0.aks0-14 is not higher than Source 3.15.0.aks0-14
12 tasks
microsoft-github-policy-service
Bot
added
Packaging
Automatic PR
3.0-dev
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an auto-generated pull request to cherry-pick commit 4e79327 to 3.0-dev. Original PR: #17761
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.