Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Apache Syncope has an Improper Isolation or Compartmentalization vulnerabilityGHSA-gq7g-vg2q-jvq3

HIGH

GHSA-gq7g-vg2q-jvq3 is a high-severity (CVSS 7.2) CWE-653 vulnerability in org.apache.syncope.core:syncope-core-spring. A fix is available for org.apache.syncope.core:syncope-core-spring — see the affected versions and patch details below.

Also known asCVE-2026-42782
Published
Updated
Affected
3 pkgs
Patched
2 / 3
Exploits
None indexed
Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-gq7g-vg2q-jvq3.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk
0.00%0.45%0.91%1.36%0.1%0.9%Jun 26Sep 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-gq7g-vg2q-jvq3 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 384,534 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected
☕org.apache.syncope.core:syncope-core-spring☕org.apache.syncope.core:syncope-core-spring☕org.apache.syncope.core:syncope-core-spring

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.syncope.core:syncope-core-spring≥ 3.0.0-M0No fix
☕Mavenorg.apache.syncope.core:syncope-core-spring≥ 4.0.0-M0&&< 4.0.64.0.6org.apache.syncope.core:syncope-core-spring:4.0.6
☕Mavenorg.apache.syncope.core:syncope-core-spring≥ 4.1.0-M0&&< 4.1.14.1.1org.apache.syncope.core:syncope-core-spring:4.1.1

Affected Products

1 product · 3 configurations
Application
syncopeapache
≥ 4.0.0 && ≤ 3.0.16
1 version
4.1.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.syncope.core:syncope-core-spring, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    No patched version of org.apache.syncope.core:syncope-core-spring has shipped for GHSA-gq7g-vg2q-jvq3 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-gq7g-vg2q-jvq3 in your dependencies?

Find it across Maven, including transitive dependencies.

Apache Syncope has an Improper Isolation or…