GraphQL Core Schema: critical account takeover
If you run a decoupled Drupal frontend, there's a decent chance a GraphQL server sits between it and your content. On November 11 the Drupal Security Team published SA-CONTRIB-2026-316 (CVE-2026-126725) for the GraphQL Core Schema module, rated Critical, and the mechanism is the kind of thing I'd want to check on my own sites before lunch.
What the advisory says
According to the advisory, the module does not sufficiently check access when a user's password is changed through the GraphQL API. Anyone who can view another user's account can change that account's password, administrators included, which leads to full account takeover. Affected versions are everything earlier than 1.0.29, and the fix is simply upgrading to 1.0.29.
The risk score is 15/25 (AC:Basic/A:User/CI:Some/II:All/E:Theoretical/TD:Default). Two details matter in practice: exploitation needs a user-level account, so it isn't anonymous, and the advisory notes default configurations are exploitable. There's no public exploit listed at publication time.
The condition that gates it
The flaw is only reachable if the "User Login" schema extension is enabled on a GraphQL server. That extension is what exposes the login and password mutations, so it's the one a headless login or account-settings page tends to switch on. If you only expose content queries, this advisory doesn't apply to you.
Check with Drush before doing anything else:
drush pm:list --status=enabled | grep -i graphql
composer show drupal/graphql_core_schema
Then look at each GraphQL server's configuration under the admin UI and see which extensions are ticked.
Fix, or mitigate if you can't deploy yet
The fix is a normal Composer update:
composer update drupal/graphql_core_schema --with-dependencies
drush updb -y && drush cr
If you can't ship today, the advisory's mitigation is to disable the "User Login" extension on your GraphQL servers. The catch, stated in the advisory itself: that also removes the login and password mutations, so a decoupled frontend that authenticates through GraphQL will break until it's re-enabled on a patched version.
What I take from it
The pattern is familiar: the authorization check that exists on the normal "edit user" form didn't carry over to a second entry point that does the same thing. Whenever an API layer re-exposes an operation Drupal already guards, I now ask what the new path checks, rather than assuming it inherits the old one. Also worth noting that this was one critical item in a batch of 24 contrib advisories released the same day, so it would be easy to miss in the noise. If GraphQL is anywhere in your stack, go and look.