cve.bz

CVE-2025-65998 apache syncope: Use of Hard-coded Cryptographic Key

7.5 highEPSS 0.5%Fix available

High (7.5) in apache syncope. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.syncope:syncope-core 3.0.15, 4.0.3.

On this page
Apache Syncope can be configured to store the user password values in the internal database with AES encryption, though this is not the default option. When AES is configured, the default key value, hard-coded in the source code, is always used. This allows a malicious attacker, once obtained access to the internal database content, to reconstruct the original cleartext password values. This is not affecting encrypted plain attributes, whose values are also stored using AES encryption. Users are recommended to upgrade to version 3.0.15 / 4.0.3, which fix this issue.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 45th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-11-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-321 Use of Hard-coded Cryptographic Key
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-65998 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-65998?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-65998?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-65998 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-65998

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-65998](https://cve.bz/cve/badge/CVE-2025-65998.svg)](https://cve.bz/cve/CVE-2025-65998)

HTML:

<a href="https://cve.bz/cve/CVE-2025-65998"><img src="https://cve.bz/cve/badge/CVE-2025-65998.svg" alt="CVE-2025-65998"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Syncopefrom 2.1 through 2.1.14
Apache Software Foundation Apache Syncopefrom 3.0 through 3.0.14
Apache Software Foundation Apache Syncopefrom 4.0 through 4.0.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jqg8-m35q-jh7jMavenorg.apache.syncope:syncope-core>=4.0.0 <4.0.34.0.3
GHSA-jqg8-m35q-jh7jMavenorg.apache.syncope:syncope-core<3.0.153.0.15

References

Check your stackJSON