Fixing Swagger 2.1.36 CVE #1045
Merged
Conversation
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
Signed-off-by: Ricardo Zanini <[email protected]>
fjtirado
approved these changes
Dec 11, 2025
Collaborator
fjtirado
left a comment
fjtirado
left a comment
There was a problem hiding this comment.
I now wondering if we should use swagger to parse the open api file at all (rhino?)
Member
Author
I was wondering the same. This thing brings A LOT OF dependencies. It's insane. Wondering if just jackson would do. |
Collaborator
|
Maybe we should try this one https://github.com/openapi-processor/openapi-parser/tree/master/openapi-parser, but it does not cover openapi 2.0 files. |
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.
A few libraries from Swagger has CVEs and the upstream project has not upgraded yet. Once they do, we can remove the forced deps.