[GHSA-hwqh-2684-54fc] Spring Cloud Gateway's SSL bundle configuration silently bypassed#7391
Merged
advisory-database[bot] merged 1 commit intoscottfrederick/advisory-improvement-7391from Apr 14, 2026
Conversation
github-actions
bot
changed the base branch from
main
to
scottfrederick/advisory-improvement-7391
advisory-database
bot
merged commit 0d2f172
into
scottfrederick/advisory-improvement-7391
4 checks passed
Contributor
|
Hi @scottfrederick! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future! |
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.
Updates
Comments
This CVE affects exactly one version of Spring Cloud Gateway - version 4.2.0. Versions before 4.2.0 were not affected, and the issue was fixed in version 4.2.1.