Add NRDAX-T0185 reference to RUSTSEC-2026-0185 (quinn-proto) - #3155
Open
simonmorley wants to merge 1 commit into
Open
Add NRDAX-T0185 reference to RUSTSEC-2026-0185 (quinn-proto)#3155simonmorley wants to merge 1 commit into
simonmorley wants to merge 1 commit into
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
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.
Adds a
referencesentry for NRDAX-T0185 to the existing quinn-proto advisory. No other field is touched.NRDAX-T0185 catalogues the mechanism this advisory describes, unbounded retention of non-contiguous stream fragments that never become deliverable, and classifies it under memory amplification within a public registry of node-infrastructure failure techniques. The entry records the qualifying conditions the advisory sets out and gives the record a stable identifier in that taxonomy alongside its existing CVE and GHSA aliases.
To be explicit about scope: this is a single-implementation entry, so the reference adds classification rather than a sibling case, and it makes no claim beyond what this advisory and its linked sources already state.
No change to
package,date,url,categories,cvss,keywords,aliasesor the patched version range.