[AUTO-CHERRYPICK] [AUTOPATCHER-CORE] Upgrade cups to 2.4.17 CVE-2026-39316, CVE-2026-39314, CVE-2026-34979, CVE-2026-34980, CVE-2026-34978, CVE-2026-27447, CVE-2026-34990 - branch 3.0-dev#16730
Merged
CBL-Mariner-Bot merged 1 commit into3.0-devfrom Apr 17, 2026
Conversation
CBL-Mariner-Bot
added
the
Auto Fast-track Cherry-pick
microsoft-github-policy-service
Bot
added
Packaging
3.0-dev
AkarshHCL
pushed a commit
to AkarshHCL/azurelinux
that referenced
this pull request
Apr 27, 2026
… CVE-2026-39316, CVE-2026-39314, CVE-2026-34979, CVE-2026-34980, CVE-2026-34978, CVE-2026-27447, CVE-2026-34990 - branch 3.0-dev" microsoft#16730 Co-authored-by: jslobodzian <joslobo@microsoft.com>
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
1 participant
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 b83c2b0 to 3.0-dev. Original PR: #16725
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.