Quick answers
- Is CVE-2026-107263 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107263 being exploited in the wild.
- How severe is CVE-2026-107263?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Drupal Gutenberg <2.15.0 or >=3.0.0 <3.0.7; Packagist:Https://Packages.Drupal.Org/8 Drupal/Gutenberg ECOSYSTEM:introduced=0,fixed=2.15.0|ECOSYSTEM:introduced=3.0.0,fixed=3.0.7.
- Is there a fix for CVE-2026-107263?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Gutenberg: upgrade to 2.15.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107263 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-107263?
- Check whether you run Drupal Gutenberg or Packagist:Https://Packages.Drupal.Org/8 Drupal/Gutenberg 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/Gutenberg: upgrade to 2.15.0 or later
Technical details
The module does not sufficiently check entity access controls in multiple editor API endpoints. The vulnerability requires an attacker to possess a Drupal role with the "use gutenberg" permission, limiting exposure to authenticated users with editing privileges. An attacker meeting this precondition can bypass per-entity access controls to view or manipulate unauthorized content through the endpoints.
Affected products
- Drupal Gutenberg <2.15.0 or >=3.0.0 <3.0.7
Identifiers
- CVE-2026-107263
- DRUPAL-CONTRIB-2026-202
Timeline
- 2026-10-07: disclosed