GHSA-qwww-vcr4-c8h2: split affected range — fix backported to react-router 7.18.2 - #8936
Open
BenjaminLimb wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
BenjaminLimb/advisory-improvement-8936
August 2, 2026 04:00
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the React Router advisory to recognize the v7 security-fix backport.
Changes:
- Splits affected ranges for React Router 7.x and 8.x.
- Marks
7.18.2as the first patched v7 release. - Adds supporting backport and release references.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Summary
GHSA-qwww-vcr4-c8h2currently declares a single affected range of>= 7.12.0, < 8.3.0with a first patched version of8.3.0. Because that range spans the 7.x and 8.x lines continuously, it marks every 7.x release above 7.12.0 as unpatched — includingreact-router@7.18.2, which carries the fix backported to the v7 branch.The advisory record was last modified
2026-07-24T16:44:43Z. The v7 backport merged2026-07-28T20:52:11Z, four days later, so the record predates it.Upstream evidence
mainis commit7a71c728(PR #15311), released inreact-router@8.3.0. That part of the record is correct.v7on 2026-07-28 as commit8ebd5df, closing #15348 which requested exactly this.packages/react-router/lib/rsc/server.rsc.ts, with the same remediation: the CSRF check'scatchnow downgrades the request toGETbeforequery()runs, so no route action can execute on a request flagged as a potential CSRF attack. The two diffs are equivalent apart from an added explanatory comment.react-router@7.18.2tag (published 2026-07-28T21:53:57Z); comparing8ebd5df...react-router@7.18.2isbehind_by: 0. Readingserver.rsc.tsat each tag shows the vulnerable shape at7.18.1and the fixed shape at7.18.2.7.18.2is the highest published 7.x release and is the currentversion-7dist-tag on npm;8.0.0is the lowest published 8.x release.The v7 line was genuinely affected — the vulnerable code is present at 7.18.1 — so the 7.x range should be retained rather than removed, with its own fixed version.
Requested change
Split the single range into two per-branch
affectedentries:>= 7.12.0, < 7.18.2, first patched7.18.2>= 7.12.0, < 8.3.0, first patched8.3.0>= 8.0.0, < 8.3.0, first patched8.3.0The
introducedboundary of7.12.0and the8.3.0fixed version are left unchanged.Also adds two references supporting the new range: the backport PR (#15353) and the
react-router@7.18.2release tag.This follows the same per-branch
affectedmodelling already used elsewhere in this repository for packages with concurrently maintained major lines (for exampleGHSA-68g3-v927-f742).