Quick answers
- Is CVE-2026-118562 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118562 being exploited in the wild.
- How severe is CVE-2026-118562?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Drupal Single Content Sync before 1.4.19; Packagist:Https://Packages.Drupal.Org/8 Drupal/Single Content Sync ECOSYSTEM:introduced=0,fixed=1.4.19.
- Is there a fix for CVE-2026-118562?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Single Content Sync: upgrade to 1.4.19 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118562 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118562?
- Check whether you run Drupal Single Content Sync or Packagist:Https://Packages.Drupal.Org/8 Drupal/Single Content Sync 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/Single Content Sync: upgrade to 1.4.19 or later
Technical details
The vulnerability is an unsafe deserialization flaw triggered when processing import files. An authenticated attacker with the "import single content" permission can craft a malicious import file containing serialized PHP objects that execute arbitrary code during deserialization. The attack requires authenticated access with a specific role, reducing but not eliminating the risk in shared hosting or multi-user environments.
Affected products
- Drupal Single Content Sync before 1.4.19
Identifiers
- CVE-2026-118562
- DRUPAL-CONTRIB-2026-275
Timeline
- 2026-10-28: disclosed