CVE-2026-118547: drupal/content_synchronizer · The Content Synchronizer module allows content to be exported and imported between Drupal sites via
Affects drupal/content_synchronizerSource GCVE Database
Not known to be exploited : upgrade to 4.1.1 soon.
Data as of 4 Nov 2026, 21:07 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 4.1.1
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Upgrade drupal/content_synchronizer to 4.1.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagist https //packages.drupal.org/8drupal/content_synchronizer | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the Content Synchronizer module to version 4.1.1 or later, where this vulnerability has been fixed. No other mitigation steps are indicated as the patch fully addresses the issue.
Description
The Content Synchronizer module for Drupal allows content export and import between sites using archive files. A vulnerability exists where a maliciously crafted import file can trigger PHP Object Injection through unsafe deserialization of untrusted data. This can potentially lead to remote code execution. The issue affects versions prior to 4.1.1 and has been fixed in version 4.1.1.