CVE-2026-118562: drupal/single_content_sync · Single Content Sync enables exporting and importing content, referenced entities, and files between
Affects drupal/single_content_syncSource GCVE Database
Not known to be exploited : upgrade to 1.4.19 soon.
Data as of 28 Oct 2026, 20:42 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 1.4.19
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade drupal/single_content_sync to 1.4.19.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagist https //packages.drupal.org/8drupal/single_content_sync | 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 Single Content Sync module to version 1.4.19 or later, where the vulnerability is fixed. Ensure that the "import single content" permission is only granted to trusted users to reduce risk.
Description
A vulnerability in the Drupal Single Content Sync module allows remote code execution via deserialization of untrusted data in a maliciously crafted import file. Exploitation requires the attacker to have the "import single content" permission. The issue is fixed in version 1.4.19.