A site maintainer traces an exposed account path blocked by a broken authorization gate while a repaired software package sits on the desk

Editorial illustration; the security symbols are conceptual, not a live site or exploit.

Drupal site owners using GraphQL Core Schema should check one specific combination: an affected module release and an enabled User Login schema extension. Drupal’s November 11, 2026 advisory says versions below 1.0.29 do not sufficiently check access when changing a user’s password through the GraphQL API. A user who can view another account could change that account’s password, including an administrator’s. The advisory lists this as Critical, 15/25, and names CVE-2026-126725. Drupal SA-CONTRIB-2026-316

This is a contributed-module advisory, not a Drupal core vulnerability. The key task is therefore to verify the module and extension in your own site, then update that component or apply the advisory’s temporary mitigation.

Summary

  • Affected context: GraphQL Core Schema below 1.0.29, when its User Login schema extension is enabled.
  • Potential impact: an eligible user may change another user’s password through GraphQL, including an administrator account.
  • Fix: update GraphQL Core Schema to 1.0.29 or later and verify the deployed version.
  • If an immediate update is not possible: review disabling the User Login extension; test frontend dependencies and treat this as a temporary mitigation.
  • The Drupal advisory’s 15/25 risk rating is not a CVSS score. I found no NVD CVSS or EPSS score in the sources checked for this article, and the CVE did not appear in CISA’s KEV catalog when checked on November 16, 2026.

What the advisory confirms

Drupal Security Advisory SA-CONTRIB-2026-316 was published on November 11, 2026. The affected project is the contributed graphql_core_schema module. Drupal identifies versions earlier than 1.0.29 as affected and recommends installing the latest version, with 1.0.29 as the first fixed release. The stated condition is that the GraphQL server has the User Login schema extension enabled. Drupal advisory listing

The advisory describes an authorization check missing from password changes through the GraphQL API. Its impact is not simply that “GraphQL is insecure”; it depends on this module, the affected version, the login extension and the account-view relationship described by the advisory. A site that does not use this module is not affected by this particular advisory. A site with the module but without the extension should still confirm the configuration and upgrade plan with its maintainer, but the advisory’s stated mitigating condition is absent.

The Drupal risk scale shown on the advisory is 15 out of 25 and labels the issue Critical. Do not restate this as “CVSS 15” or convert it into a 0–10 CVSS score. CVE-2026-126725 is the shared vulnerability identifier; the Drupal advisory is the direct source for Drupal’s affected range and remediation. NVD’s public detail page did not expose readable scoring data in my check, and FIRST’s EPSS API returned no score for this CVE at the time checked. These gaps are not evidence that the issue is harmless.

Check whether your site matches the affected setup

Start in the production codebase and its deployed configuration, not only in an admin screen. The Drupal Composer update workflow covers rehearsing a core update; use the same lockfile review and staging discipline for this contributed-module fix. If you need to verify who should see user accounts, revisit the Drupal roles and permissions audit.

  1. Check the dependency. Look at composer.lock or run composer show drupal/graphql_core_schema from the deployed project to identify the installed release. Confirm that it is below 1.0.29; also check the release constraints supported by your project before changing it.
  2. Check the extension. Inspect the GraphQL server’s schema configuration and determine whether the User Login extension is enabled. A decoupled frontend or mobile application may depend on its login and password mutations, so identify consumers before disabling it.
  3. Check exposure and access. Confirm which GraphQL endpoint is reachable, which roles can view user accounts, and whether those roles are intended to have that access. These checks help establish exposure and impact; they do not make an affected release safe.
  4. Check other environments. Staging, preview and secondary production sites often use a separate Composer lockfile, image or deployment pipeline. Include them in the inventory so an old build is not left online.

If the installed version cannot be confirmed, treat the result as unknown and trace the deployed artifact to its build input. A repository’s current lockfile is not proof that every running container has been rebuilt.

Update safely to 1.0.29 or later

Use the project’s Composer workflow to require the fixed release within existing constraints. Review the solver output before deployment: a module update can change transitive dependencies or reveal a compatibility constraint that needs a planned code change. Avoid editing composer.lock by hand.

Deploy to a staging environment that mirrors the production schema and configuration. Test the GraphQL operations the site actually uses: expected login behavior, password changes for the signed-in user, authorization around other accounts, and any frontend queries or mutations that rely on the module. Do not use a real customer account or password for the test. Review application logs for errors, then promote the tested artifact through the normal release process.

After rollout, verify the running module reports 1.0.29 or later in every relevant environment. Smoke-test the GraphQL endpoint and confirm that normal login and account-management flows still work. Keep a rollback plan for application availability, but do not roll back to an affected release without explicitly accepting that security exposure and adding a short-lived, verified control.

If you cannot update right now

Drupal’s advisory identifies disabling the User Login schema extension as the mitigation. This can remove GraphQL login or password operations needed by a decoupled application, so first map its consumers and test the fallback authentication path. If the extension is disabled, verify in the deployed environment that the vulnerable mutations are no longer available; do not rely on a change made only in source configuration.

Record who owns the update, why it is delayed, which control is active, who will verify it, and the date by which the fixed release must be installed. A temporary mitigation reduces the relevant attack path; it does not correct the vulnerable module code or replace the upgrade.

What the CVE status does and does not say

The CVE-2026-126725 identifier lets security tools and maintainers correlate records about this vulnerability. It does not itself contain the complete Drupal update instructions. CVSS measures technical severity; EPSS estimates near-term exploitation likelihood; CISA KEV is a list of vulnerabilities CISA identifies as exploited in the wild. They answer different questions.

As checked on November 16, 2026, this CVE was not present in the CISA KEV feed, and FIRST’s EPSS API returned no record. That means these sources did not give a positive exploitation signal at that check time. It does not rule out private exploitation, later inclusion, or a local attack path. Recheck the official sources during triage because their data changes.

My Take

For this advisory, the fastest useful first check is usually the GraphQL server configuration: does this site enable the User Login extension? Pair that with the installed module version rather than debating the headline severity in isolation. If both conditions match, schedule the fixed release promptly and test the frontend’s authentication flow as part of the patch.

Bottom Line

If your Drupal site uses GraphQL Core Schema below 1.0.29 with the User Login extension enabled, update to 1.0.29 or later. If you must delay, assess and verify the advisory’s mitigation by disabling that extension, then set a dated plan to deploy the fixed code.

Sources