[GHSA-xwmg-2g98-w7v9] Nimbus JOSE + JWT is vulnerable to DoS attacks when processing deeply nested JSON - #9087
Open
tal-sealsecurity wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
tal-sealsecurity/advisory-improvement-9087
August 12, 2026 10:44
|
GitHub is not the issuer of the CVE. If you want it updated, then you should contact MITRE via their form. |
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.
Updates
Comments
I am submitting a correction regarding the technical details and attribution of CVE-2025-53864. The official NVD description contains a note stating that this vulnerability is independent of the underlying JSON parser limits. Code analysis of the official patches proves this note is factually incorrect.
The current advisory states:
"NOTE: this is independent of the Gson 2.11.0 issue because the Connect2id product could have checked the JSON object nesting depth, regardless of what limits (if any) were imposed by Gson."
this is not actually a vuln in the codebase of nimbus but a vuln in its dependency