# CVE-2025-57738: Apache Syncope: Remote Code Execution by delegated administrators > Malicious administrators can inject Groovy code to achieve remote code execution on Apache Syncope instances. - **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Oct 2025 - **Updated:** 4 Nov 2025 - **Also known as:** GHSA-825g-mm5v-ggq4 ## What is CVE-2025-57738? CVE-2025-57738 is a high-severity code injection vulnerability in Apache Syncope, published on 20 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description Apache Syncope offers the ability to extend / customize the base behavior on every deployment by allowing to provide custom implementations of a few Java interfaces; such implementations can be provided either as Java or Groovy classes, with the latter being particularly attractive as the machinery is set for runtime reload. Such a feature has been available for a while, but recently it was discovered that a malicious administrator can inject Groovy code that can be executed remotely by a running Apache Syncope Core instance. Users are recommended to upgrade to version 3.0.14 / 4.0.2, which fix this issue by forcing the Groovy code to run in a sandbox. Weakness: CWE-653 (Improper Isolation or Compartmentalization) ## Which versions are affected by CVE-2025-57738? 4 open source packages ship an affected version, including org.apache.syncope.core:syncope-core-spring. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.syncope.core:syncope-core-spring` | Maven | All versions | 3.0.14 | | `org.apache.syncope.core:syncope-core-spring` | Maven | All versions | 3.0.14 | | `org.apache.syncope.core:syncope-core-spring` | Maven | From 4.0.0-M0 | 4.0.2 | | `org.apache.syncope.core:syncope-core-spring` | Maven | From 4.0.0-M0 | 4.0.2 | Products: Apache Syncope. ## How do I fix CVE-2025-57738? Upgrade org.apache.syncope.core:syncope-core-spring to a fixed version for your release line: 3.0.14 or 4.0.2. ## Is CVE-2025-57738 being exploited? There is no known exploitation of CVE-2025-57738 in the wild and no public exploit code. ## Other vulnerabilities in Apache Syncope - [CVE-2026-53405](https://insights.sbomify.com/CVE-2026-53405/): Apache Syncope: Remote Code Execution via Flowable BPMN Groovy ScriptTask (critical 9.8) - [CVE-2026-53421](https://insights.sbomify.com/CVE-2026-53421/): Apache Syncope: Remote Code Execution via Scripted Connector (critical 9.8) - [CVE-2026-57308](https://insights.sbomify.com/CVE-2026-57308/): Apache Syncope: SQL injection vulnerability in Audit Events search (critical 9.8) - [CVE-2026-62183](https://insights.sbomify.com/CVE-2026-62183/): Apache Syncope: User self-service privilege escalation (critical 9.8) - [CVE-2026-63071](https://insights.sbomify.com/CVE-2026-63071/): Apache Syncope: RCE via Groovy Sandbox bypass (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-57738 and fix it if it is affected. What it is: CVE-2025-57738 is a high-severity code injection vulnerability in Apache Syncope, published on 20 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-57738 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.syncope.core:syncope-core-spring (Maven): affected all versions; fixed in 3.0.14 - org.apache.syncope.core:syncope-core-spring (Maven): affected all versions; fixed in 3.0.14 - org.apache.syncope.core:syncope-core-spring (Maven): affected from 4.0.0-M0; fixed in 4.0.2 - org.apache.syncope.core:syncope-core-spring (Maven): affected from 4.0.0-M0; fixed in 4.0.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-57738/ (Markdown: https://insights.sbomify.com/CVE-2025-57738/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-57738 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-57738 - OSV: https://osv.dev/vulnerability/CVE-2025-57738 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-57738/ Summaries are generated and may contain mistakes; the official description above is the record.