---
id: CVE-2026-77147
title: >-
  Improper Control of Generation of Code ('Code Injection') vulnerability in
  Apache Syncope.


  An administrator with adequate entitlements for Implementations can create a
  malicious Groovy Command class containing untrusted code in their Co…
summary: >-
  Improper Control of Generation of Code ('Code Injection') vulnerability in
  Apache Syncope.


  An administrator with adequate entitlements for Implementations can create a
  malicious Groovy Command class containing untrusted code in their Co…
severity: medium
cvss: 6.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N'
cwe:
  - CWE-94
vendor: Apache Software Foundation
product: 'org.apache.syncope.core:syncope-core-spring'
affected:
  - 'org.apache.syncope.core:syncope-core-spring >= 3.0.0-M0 <= 3.0.16'
  - 'org.apache.syncope.core:syncope-core-spring >= 4.0.0-M0 <= 4.0.7'
  - 'org.apache.syncope.core:syncope-core-spring >= 4.1.0-M0 <= 4.1.2'
published: '2026-09-14'
updated: '2026-09-14'
sourceUpdated: '2026-09-14T20:58:48.430'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-77147'
references:
  - url: 'https://lists.apache.org/thread/qr464o2lyj3rxp8b0q25ssn0qwjxyrgz'
    label: security@apache.org
  - url: 'http://www.openwall.com/lists/oss-security/2026/09/14/15'
    label: af854a3a-2127-422b-91ae-364da2661108
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-09-14T14:02:24.262560Z'
ingestedAt: '2026-09-14T15:23:07.421Z'
epss: 0.00284
epssPercentile: 0.21145
---

## Overview

Improper Control of Generation of Code ('Code Injection') vulnerability in Apache Syncope.

An administrator with adequate entitlements for Implementations can create a malicious Groovy Command class containing untrusted code in their CommandArgs static implementation, bypassing the Groovy security sandbox.

This issue affects Apache Syncope: from 3.0.0-M0 through 3.0.16, from 4.0.0-M0 Through 4.0.7, from 4.1.0-M0 through 4.1.2.

Users are recommended to upgrade to version 4.0.8 / 4.1.3, which fix this issue.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.