---
id: "CVE-2026-113687"
kind: "vulnerability"
aliases: ["CVE-2026-113687"]
title: "Apache Syncope: admin-created Groovy class escapes sandbox by running on new thread"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-syncope", "groovy", "identity-management", "java", "package"]
not_affected_if: ["fixed-version", "no-implementation-entitlements"]
published_at: "2026-11-02T14:17:35+00:00"
first_seen_at: "2026-11-02T14:23:23+00:00"
updated_at: "2026-11-02T14:24:56+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-113687", "first_seen_at": "2026-11-02T14:23:23+00:00"}]
---

# Apache Syncope: admin-created Groovy class escapes sandbox by running on new thread

An administrator with entitlements for Implementations can create a Groovy class that runs untrusted code on a separate thread, bypassing the Groovy security sandbox. The attacker gets arbitrary code execution in the Syncope process beyond what the sandbox was meant to allow.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Apache Syncope version in use: `unknown` if not visible, otherwise compare against the affected ranges 3.0.0-M0 to 3.0.16, 4.0.0-M0 to 4.0.8, and 4.1.0-M0 to 4.1.3.
- Check which accounts hold entitlements for Implementations in the Syncope admin console.

## Fix

- Apache Syncope `4.0.9` (for the 4.0 line)
- Apache Syncope `4.1.4` (for the 4.1 line)

## Timeline

- 2026-11-02T14:23:23+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-113687

## From the sources

Improper isolation or compartmentalization vulnerability in Apache Syncope.



An administrator with adequate entitlements for Implementations can create a malicious Groovy class running untrusted code on a separate Thread, thus 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.8, from 4.1.0-M0 through 4.1.3.



Users are recommended to upgrade to version 4.0.9 / 4.1.4, which fix this issue.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_