GHSA-p46v-f2x8-qp98: add fixed event 2.0.0-rc3 for github.com/prest/p… - #9046
Open
DTDucas wants to merge 1 commit into
Open
GHSA-p46v-f2x8-qp98: add fixed event 2.0.0-rc3 for github.com/prest/p…#9046DTDucas wants to merge 1 commit into
DTDucas wants to merge 1 commit into
Conversation
…rest/v2
The record states the module is affected below 2.0.0-rc2 and carries no fixed
event. Both halves are inaccurate: 2.0.0-rc2 is itself affected, and the fixed
version is known precisely.
- 2.0.0-rc2 was published 2025-02-18. The fix commit referenced by this
advisory, 47d02b87 ("fix(postgres): improve `_returning` param handling for
SQL injection safety"), is dated 2025-09-08 — nearly seven months later, so
rc2 cannot contain it.
- `compare/v2.0.0-rc2...47d02b87` reports "ahead": rc2 does not contain the fix.
- `compare/v2.0.0-rc3...47d02b87` reports "identical": tag v2.0.0-rc3 is that
exact commit. It was published 2025-09-08, the same day, and is therefore the
first version carrying the fix.
- Every later release contains it: rc4, rc5, rc6, 2.0.0, 2.1.0, 2.2.0, 2.3.0,
2.4.0 and 2.4.1 all report "behind" against the fix commit.
With no fixed event the advisory reports no patch available, even though
2.0.0-rc3 has been out since September 2025 and 2.4.1 is the current release.
Adding it also brings 2.0.0-rc2 inside the affected range, where it belongs.
`database_specific.last_known_affected_version_range` is removed because the
fixed version is now asserted; the field exists to record that it is unknown.
github-actions
Bot
changed the base branch from
main
to
DTDucas/advisory-improvement-9046
August 11, 2026 08:57
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.
…rest/v2
The record states the module is affected below 2.0.0-rc2 and carries no fixed event. Both halves are inaccurate: 2.0.0-rc2 is itself affected, and the fixed version is known precisely.
_returningparam handling for SQL injection safety"), is dated 2025-09-08 — nearly seven months later, so rc2 cannot contain it.compare/v2.0.0-rc2...47d02b87reports "ahead": rc2 does not contain the fix.compare/v2.0.0-rc3...47d02b87reports "identical": tag v2.0.0-rc3 is that exact commit. It was published 2025-09-08, the same day, and is therefore the first version carrying the fix.With no fixed event the advisory reports no patch available, even though 2.0.0-rc3 has been out since September 2025 and 2.4.1 is the current release. Adding it also brings 2.0.0-rc2 inside the affected range, where it belongs.
database_specific.last_known_affected_version_rangeis removed because the fixed version is now asserted; the field exists to record that it is unknown.