Vulnerability Database · Maven · Package report

org.apache.syncope:syncope-core: vulnerability history, versions and safety

org.apache.syncope:syncope-core is a package in the Maven ecosystem. Vulert records 7 vulnerabilities for it across 66 releases, from Nov 2018 to Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded C1 H4 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 24 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.apache.syncope:syncope-core 4.1.3 i

Updated on 23 Oct 2026

Good news: 4.1.3, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 7.

Package health score 69/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 4.1.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.1.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.1.3 — unaffected i
  • Vulnerabilities on record 7 over 7 years · 1 in the last year i
  • Latest disclosure 24 Nov 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.apache.syncope:syncope-core, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.0.8 11 Sep 2026 none Apache-2.0 — Details →
4.1.3 11 Sep 2026 none Apache-2.0 — Details →
4.0.7 17 Jul 2026 none Apache-2.0 — Details →
4.1.2 17 Jul 2026 none Apache-2.0 — Details →
4.0.6 22 May 2026 none Apache-2.0 — Details →
4.1.1 22 May 2026 none Apache-2.0 — Details →
4.0.5 31 Mar 2026 none Apache-2.0 — Details →
4.1.0 31 Mar 2026 none Apache-2.0 — Details →
4.1.0-M0 19 Feb 2026 none Apache-2.0 — Details →
3.0.16 30 Jan 2026 none Apache-2.0 — Details →
4.0.4 30 Jan 2026 none Apache-2.0 — Details →
3.0.15 21 Nov 2025 none Apache-2.0 — Details →
4.0.3 21 Nov 2025 none Apache-2.0 — Details →
3.0.14 17 Oct 2025 none Apache-2.0 — Details →
4.0.2 17 Oct 2025 H1 Apache-2.0 Yes Details →
3.0.13 08 Aug 2025 none Apache-2.0 — Details →
4.0.1 08 Aug 2025 H1 Apache-2.0 Yes Details →
3.0.12 23 May 2025 none Apache-2.0 — Details →
4.0.0 23 May 2025 H1 Apache-2.0 Yes Details →
4.0.0-M1 07 Mar 2025 none Apache-2.0 — Details →
3.0.11 07 Mar 2025 none Apache-2.0 — Details →
4.0.0-M0 27 Dec 2024 none Apache-2.0 — Details →
3.0.10 27 Dec 2024 none Apache-2.0 — Details →
3.0.9 21 Oct 2024 none Apache-2.0 — Details →
3.0.8 19 Jul 2024 none Apache-2.0 — Details →
3.0.7 20 May 2024 none Apache-2.0 — Details →
3.0.6 22 Dec 2023 none Apache-2.0 — Details →
3.0.5 29 Sep 2023 none Apache-2.0 — Details →
3.0.4 07 Jul 2023 none Apache-2.0 — Details →
2.1.14 05 May 2023 none Apache-2.0 — Details →
3.0.3 05 May 2023 none Apache-2.0 — Details →
3.0.2 17 Feb 2023 none Apache-2.0 — Details →
3.0.1 13 Jan 2023 none Apache-2.0 — Details →
2.1.13 09 Dec 2022 none Apache-2.0 — Details →
3.0.0 11 Nov 2022 none Apache-2.0 — Details →
3.0.0-M2 27 Oct 2022 none Apache-2.0 — Details →
3.0.0-M1 14 Oct 2022 none Apache-2.0 — Details →
3.0.0-M0 05 Aug 2022 none Apache-2.0 — Details →
2.1.12 05 Aug 2022 none Apache-2.0 — Details →
2.1.11 18 Mar 2022 none Apache-2.0 — Details →
2.1.10 08 Oct 2021 none Apache-2.0 — Details →
2.1.9 07 Apr 2021 none Apache-2.0 — Details →
2.1.8 18 Dec 2020 none Apache-2.0 — Details →
2.0.16 11 Sep 2020 C1 Apache-2.0 Yes Details →
2.1.7 11 Sep 2020 none Apache-2.0 — Details →
2.0.15 29 Apr 2020 C1 Apache-2.0 Yes Details →
2.1.6 29 Apr 2020 none Apache-2.0 — Details →
2.0.14 12 Sep 2019 C1 H1 Apache-2.0 Yes Details →
2.1.5 12 Sep 2019 C1 Apache-2.0 Yes Details →
2.0.13 19 Apr 2019 C1 H1 Apache-2.0 Yes Details →
2.1.4 19 Apr 2019 C1 Apache-2.0 Yes Details →
2.0.12 17 Jan 2019 C1 H1 Apache-2.0 Yes Details →
2.1.3 17 Jan 2019 C1 Apache-2.0 Yes Details →
2.0.11 02 Nov 2018 C1 H1 Apache-2.0 Yes Details →
2.1.2 02 Nov 2018 C1 Apache-2.0 Yes Details →
2.0.10 17 Aug 2018 C1 H2 M1 Apache-2.0 Yes Details →
2.1.1 17 Aug 2018 C1 Apache-2.0 Yes Details →
2.1.0 05 Jul 2018 C1 Apache-2.0 Yes Details →
2.0.9 28 Jun 2018 C1 H2 M1 Apache-2.0 Yes Details →
2.0.8 13 Mar 2018 C1 H2 M1 Apache-2.0 Yes Details →
1.2.11 13 Mar 2018 C1 H1 M1 Apache-2.0 Yes Details →
2.0.7 22 Dec 2017 C1 H2 M1 Apache-2.0 Yes Details →
2.0.6 09 Oct 2017 C1 H2 M1 Apache-2.0 Yes Details →
2.0.5 06 Sep 2017 C1 H2 M1 Apache-2.0 Yes Details →
2.0.4 03 Jul 2017 C1 H2 M1 Apache-2.0 Yes Details →
2.0.3 15 Apr 2017 C1 H2 M1 Apache-2.0 Yes Details →
2.0.2 27 Jan 2017 C1 H2 M1 Apache-2.0 Yes Details →
1.2.10 24 Jan 2017 C1 H2 M2 Apache-2.0 Yes Details →
2.0.1 21 Oct 2016 C1 H2 M1 Apache-2.0 Yes Details →
1.2.9 07 Oct 2016 C1 H2 M2 Apache-2.0 Yes Details →
2.0.0 09 Sep 2016 C1 H2 M1 Apache-2.0 Yes Details →
2.0.0.M5 02 Sep 2016 C1 H1 M1 Apache-2.0 Yes Details →
2.0.0-M4 24 Jun 2016 C1 H1 M1 Apache-2.0 Yes Details →
2.0.0-M3 03 Jun 2016 C1 H1 M1 Apache-2.0 Yes Details →
1.2.8 03 Jun 2016 C1 H2 M2 Apache-2.0 Yes Details →
2.0.0-M2 21 Mar 2016 C1 H1 M1 Apache-2.0 Yes Details →
1.2.7 15 Jan 2016 C1 H2 M2 Apache-2.0 Yes Details →
2.0.0-M1 23 Dec 2015 C1 H1 M1 Apache-2.0 Yes Details →
1.2.6 05 Nov 2015 C1 H2 M2 Apache-2.0 Yes Details →
1.2.5 28 Jul 2015 C1 H2 M2 Apache-2.0 Yes Details →
1.2.4 05 May 2015 C1 H2 M2 Apache-2.0 Yes Details →
1.2.3 20 Mar 2015 C1 H2 M2 Apache-2.0 Yes Details →
1.2.2 30 Jan 2015 C1 H2 M2 Apache-2.0 Yes Details →
1.2.1 17 Nov 2014 C1 H2 M2 Apache-2.0 Yes Details →
1.2.0 03 Oct 2014 C1 H2 M2 Apache-2.0 Yes Details →
1.2.0-M1 08 Sep 2014 C1 H2 M2 Apache-2.0 Yes Details →
1.1.8 03 Jul 2014 C1 H2 M2 Apache-2.0 Yes Details →
1.1.7 11 Apr 2014 C1 H2 M2 Apache-2.0 Yes Details →
1.0.9 11 Apr 2014 C1 H2 M2 Apache-2.0 Yes Details →
1.1.6 22 Feb 2014 C1 H2 M2 Apache-2.0 Yes Details →
1.1.5 28 Nov 2013 C1 H2 M2 Apache-2.0 Yes Details →
1.1.4 27 Sep 2013 C1 H2 M2 Apache-2.0 Yes Details →
1.1.3 12 Jul 2013 C1 H2 M2 Apache-2.0 Yes Details →
1.1.2 11 Jun 2013 C1 H2 M2 Apache-2.0 Yes Details →
1.1.1 29 Apr 2013 C1 H2 M2 Apache-2.0 Yes Details →
1.0.8 18 Apr 2013 C1 H2 M2 Apache-2.0 Yes Details →
1.1.0 05 Apr 2013 C1 H2 M2 Apache-2.0 Yes Details →
1.0.7 26 Mar 2013 C1 H2 M2 Apache-2.0 Yes Details →
1.0.6 27 Feb 2013 C1 H2 M2 Apache-2.0 Yes Details →
1.0.5 23 Jan 2013 C1 H2 M2 Apache-2.0 Yes Details →
1.0.4 10 Dec 2012 C1 H2 M2 — Yes Details →
1.0.3-incubating 30 Oct 2012 C1 H2 M2 — Yes Details →
1.0.2-incubating 02 Oct 2012 C1 H2 M2 — Yes Details →
1.0.1-incubating 30 Aug 2012 C1 H2 M2 — Yes Details →
1.0.0-incubating 07 Aug 2012 C1 H2 M2 — Yes Details →
1.0.0-RC3-incubating 18 Jul 2012 C1 H2 M2 — Yes Details →
1.0.0-RC2-incubating 25 Jun 2012 C1 H2 M2 — Yes Details →
1.0.0-RC1-incubating 24 May 2012 C1 H2 M2 — Yes Details →

All 108 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 4
  • 2021 2
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 7 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.apache.syncope:syncope-core

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.apache.syncope:syncope-core

Is org.apache.syncope:syncope-core safe to use?

Vulert records 7 vulnerabilities for org.apache.syncope:syncope-core in Maven: 1 critical, 4 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.apache.syncope:syncope-core's Vulert package health score?

Vulert scores org.apache.syncope:syncope-core 69/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.apache.syncope:syncope-core affected?

No. 4.1.3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.apache.syncope:syncope-core should I use?

4.1.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.apache.syncope:syncope-core have?

7 vulnerabilities are recorded for org.apache.syncope:syncope-core in the Maven ecosystem: 1 critical, 4 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.apache.syncope:syncope-core vulnerabilities disclosed?

1 vulnerability was recorded for org.apache.syncope:syncope-core in the last 12 months, and the oldest entry in this database dates to 06 Nov 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.apache.syncope:syncope-core are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.apache.syncope:syncope-core for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.syncope:syncope-core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.