Skip to content

chore(deps): update dependency apollographql/router to v2.12.1#86

Merged
renovate[bot] merged 1 commit intomainfrom
renovate/apollographql-router-2.x
Mar 29, 2026
Merged

chore(deps): update dependency apollographql/router to v2.12.1#86
renovate[bot] merged 1 commit intomainfrom
renovate/apollographql-router-2.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 26, 2026

This PR contains the following updates:

Package Update Change
apollographql/router patch 2.12.02.12.1

Release Notes

apollographql/router (apollographql/router)

v2.12.1

Compare Source

🔒 Security

[!NOTE]
For more information on the impact of the fix in this release and how your deployment might be affected or remediated, see the corresponding GitHub Security Advisory (GHSA) linked below. Updating to a patched Router version will resolve any vulnerabilities.

Reject GET requests with a non-application/json Content-Type header (GHSA-hff2-gcpx-8f4p)

The router now rejects GraphQL GET requests that include a Content-Type header with a value other than application/json (with optional parameters such as ; charset=utf-8). Any other value is rejected with a 415 status code.

GET requests without a Content-Type header continue to be allowed (subject to the router's existing CSRF prevention check), since GET requests have no body and therefore technically do not require this header.

This improvement makes the router's CSRF prevention more resistant to browsers that implement CORS in non-spec-compliant ways. Apollo is aware of one browser which as of March 2026 has a bug allowing an attacker to circumvent the router's CSRF prevention to carry out read-only XS-Search-style attacks. The browser vendor is in the process of patching this vulnerability; upgrading to this version of the router mitigates the vulnerability.

If your graph uses cookies (or HTTP Basic Auth) for authentication, Apollo encourages you to upgrade to this version.

This is technically a backwards-incompatible change. Apollo is not aware of any GraphQL clients that provide non-empty Content-Type headers on GET requests with types other than application/json. If your use case requires such requests, please contact support, and we may add more configurability in a follow-up release.

By @​glasser and @​carodewig in GHSA-hff2-gcpx-8f4p


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (squash) March 26, 2026 13:00
@renovate renovate bot force-pushed the renovate/apollographql-router-2.x branch from d82f080 to 603ccc1 Compare March 29, 2026 17:32
@renovate renovate bot merged commit 75faeba into main Mar 29, 2026
2 checks passed
@renovate renovate bot deleted the renovate/apollographql-router-2.x branch March 29, 2026 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants