Is CVE-2026-126725 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-126725 being exploited in the wild.

How severe is CVE-2026-126725?

Informational severity, published 11 November 2026.

Which products and versions are affected?

Drupal GraphQL Core Schema before 1.0.29; Packagist:Https://Packages.Drupal.Org/8 Drupal/Graphql Core Schema ECOSYSTEM:introduced=0,fixed=1.0.29.

How is CVE-2026-126725 attacked?

It is attacked over the network.

Am I affected by CVE-2026-126725?

Check whether you run Drupal GraphQL Core Schema or Packagist:Https://Packages.Drupal.Org/8 Drupal/Graphql Core Schema at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-126725: Drupal GraphQL Core Schema improper authorization in password change

CVE-2026-126725 · Severity: info · Published 2026-11-11

The GraphQL Core Schema module for Drupal provides a configurable API for accessing Drupal entities and fields. A flaw in the User Login schema extension fails to properly verify permissions when changing user passwords through the GraphQL API, allowing an attacker who can view another user's account to reset that user's password, including administrator accounts, leading to complete account takeover.

Vendors: Drupal, Packagist:Https://Packages.Drupal.Org/8.

Quick answers

Is CVE-2026-126725 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-126725 being exploited in the wild.
How severe is CVE-2026-126725?: Informational severity, published 11 November 2026.
Which products and versions are affected?: Drupal GraphQL Core Schema before 1.0.29; Packagist:Https://Packages.Drupal.Org/8 Drupal/Graphql Core Schema ECOSYSTEM:introduced=0,fixed=1.0.29.
Is there a fix for CVE-2026-126725?: Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Graphql Core Schema: upgrade to 1.0.29 or later. Until then: Disable the User Login schema extension on GraphQL servers until the module can be upgraded to version 1.0.29. This prevents the password change mutations from being accessible, though it may break dependent frontend functionality. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-126725 attacked?: It is attacked over the network.
Am I affected by CVE-2026-126725?: Check whether you run Drupal GraphQL Core Schema or Packagist:Https://Packages.Drupal.Org/8 Drupal/Graphql Core Schema at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Packagist:Https://Packages.Drupal.Org/8 Drupal/Graphql Core Schema: upgrade to 1.0.29 or later

Disable the User Login schema extension on GraphQL servers until the module can be upgraded to version 1.0.29. This prevents the password change mutations from being accessible, though it may break dependent frontend functionality.

Technical details

The module performs insufficient access checks when processing password change mutations through its GraphQL API. An authenticated user with permission to view another user's account can bypass authorization checks and modify that user's password, including those of privileged accounts. This requires the User Login schema extension to be enabled and the attacker to have basic view access to user accounts.

Affected products

Drupal GraphQL Core Schema before 1.0.29

Identifiers

CVE-2026-126725
DRUPAL-CONTRIB-2026-316

Timeline

2026-11-11: disclosed
2026-11-11: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.