CVE-2026-42782GHSA-GQ7G-VG2Q-JVQ3
Apache Syncope: Post-auth RCE via Groovy static
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.0.6, 4.1.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Improper Isolation or Compartmentalization vulnerability in Apache Syncope. An administrator with adequate entitlements for Implementations can create a malicious Groovy class containing untrusted code reaching a non-sandboxed execution path via the class static initializer. This issue affects Apache Syncope: 3.0 through 3.0.16, 4.0 through 4.0.5, 4.1.0. Users are recommended to upgrade to version 4.0.6 / 4.1.1, which fix this issue by forcing even the static initializer in Groovy code to run in a sandbox.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- org.apache.syncope.core:syncope-core-spring
From 3.0 · through 3.0.16; From 4.0 · through 4.0.5; From 4.1 · through 4.1.0
- org.apache.syncope.core:syncope-core-springMaven
From 3.0.0-M0 · through 3.0.16
- org.apache.syncope.core:syncope-core-springMaven
From 4.0.0-M0 · fixed in 4.0.6
- org.apache.syncope.core:syncope-core-springMaven
From 4.1.0-M0 · fixed in 4.1.1