[RUN-4933] Bump rundeck-core to 6.2.0-20260908 (CVE-2026-19032) - #67
Open
fdevans wants to merge 1 commit into
Open
[RUN-4933] Bump rundeck-core to 6.2.0-20260908 (CVE-2026-19032)#67fdevans wants to merge 1 commit into
fdevans wants to merge 1 commit into
Conversation
rundeck-core 6.1.0-20260803 pulls in a vulnerable transitive Jackson version (CVE-2026-19032). 6.2.0-20260908 includes the fix.
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
fdevans
changed the title
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
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.
What
Bumps
rundeck-corefrom6.1.0-20260803to6.2.0-20260908.Why
CVE-2026-19032:
6.1.0-20260803pulls in a vulnerable transitiveJackson version.
6.2.0-20260908includes the fix.Note
6.2.0-20260908was published today. If the CI build here fails toresolve it, that's expected propagation lag on the Sonatype snapshots
feed, not a real problem with this change - rerun the build once it's
synced.