Insertion of sensitive information into log file vulnerability in Apache Syncope. (CVE-2026-87779)
Apache Syncope versions 3.0.15 through 3.0.16, 4.0.3 through 4.0.7, and 4.1.0-M0 through 4.1.2 contain a vulnerability where sensitive information is inserted into log files. This occurs when an AES key of non-standard length is configured, causing Syncope to pad the key with random characters and log the resulting key value. The issue is fixed in versions 4.0.8 and 4.1.3.
AI Analysis
Technical Summary
The vulnerability in Apache Syncope involves the insertion of sensitive information into log files when an AES key of non-standard length (not 16, 24, or 32 bytes) is configured. Syncope pads the provided key with random characters to reach a standard length, and this padded key value is logged, potentially exposing sensitive cryptographic material. This affects Apache Syncope versions 3.0.15 through 3.0.16, 4.0.3 through 4.0.7, and 4.1.0-M0 through 4.1.2. The issue is fixed in versions 4.0.8 and 4.1.3.
Potential Impact
The vulnerability can lead to the exposure of sensitive cryptographic key material in log files, which could be accessed by unauthorized users. This exposure compromises the confidentiality of the AES key, potentially enabling attackers to decrypt sensitive data protected by the key. The CVSS score of 7.5 reflects a high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and high confidentiality impact.
Mitigation Recommendations
Users should upgrade Apache Syncope to versions 4.0.8 or 4.1.3, where this vulnerability has been fixed. No other mitigations are specified or recommended by the vendor advisory.
Insertion of sensitive information into log file vulnerability in Apache Syncope. (CVE-2026-87779)
Description
Apache Syncope versions 3.0.15 through 3.0.16, 4.0.3 through 4.0.7, and 4.1.0-M0 through 4.1.2 contain a vulnerability where sensitive information is inserted into log files. This occurs when an AES key of non-standard length is configured, causing Syncope to pad the key with random characters and log the resulting key value. The issue is fixed in versions 4.0.8 and 4.1.3.
CVSS v3.1
Score 7.5high
Affected software
pkg:maven/org.apache.syncope/syncope-coreRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Apache Syncope involves the insertion of sensitive information into log files when an AES key of non-standard length (not 16, 24, or 32 bytes) is configured. Syncope pads the provided key with random characters to reach a standard length, and this padded key value is logged, potentially exposing sensitive cryptographic material. This affects Apache Syncope versions 3.0.15 through 3.0.16, 4.0.3 through 4.0.7, and 4.1.0-M0 through 4.1.2. The issue is fixed in versions 4.0.8 and 4.1.3.
Potential Impact
The vulnerability can lead to the exposure of sensitive cryptographic key material in log files, which could be accessed by unauthorized users. This exposure compromises the confidentiality of the AES key, potentially enabling attackers to decrypt sensitive data protected by the key. The CVSS score of 7.5 reflects a high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and high confidentiality impact.
Mitigation Recommendations
Users should upgrade Apache Syncope to versions 4.0.8 or 4.1.3, where this vulnerability has been fixed. No other mitigations are specified or recommended by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2987-fvqf-8g2j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-87779"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa8a1d055bf5e2cf5f3e93f
Added to database: 09/15/2026, 01:39:28 UTC
Last enriched: 09/15/2026, 02:03:36 UTC
Last updated: 09/15/2026, 10:01:23 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.