CVE-2026-77051: Apache Syncope: SQL injection via unsanitized entityKey and opEvent in Audit Events search
Apache Syncope patches a moderate SQL injection (CVE-2026-77051) in Audit Events search via unsanitized entityKey and opEvent inputs.
CVE-2026-77051 is a moderate-severity SQL injection vulnerability in Apache Syncope's Audit Events search, caused by unsanitized entityKey and opEvent parameters. The flaw affects syncope-core-persistence-jpa 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.7, and 4.1.0-M0 through 4.1.2. Users should upgrade to the fixed versions in each affected line.
- SQL injection in Apache Syncope Audit Events search
- Unsanitized entityKey and opEvent parameters
- Rated moderate severity
- Affects 3.0.x, 4.0.x, and 4.1.x release lines
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-77051 | Authenticated SQL Injection in Apache Syncope Audit Events Search CVE-2026-77051 is an SQL injection vulnerability (CWE-89) in Apache Syncope, an open-source identity management platform, affecting the Audit Events search feature. An authenticated administrator with adequate entitlements can inject arbitrary SQL via stacked queries by passing unsanitized entityKey and opEvent parameters, potentially reading, modifying, or destroying data in the backing database depending on the database account's privileges. Affected versions are 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.7, and 4.1.0-M0 through 4.1.2; the issue is fixed in 4.0.8 and 4.1.3 (users on the 3.0.x line have no patched 3.0 release and must upgrade). Exploitation requires administrative access, which limits the attacker pool to privileged insiders or attackers who have already compromised an admin account. No public proof-of-concept or in-the-wild exploitation is currently known, and the CVE is not in the CISA KEV catalog. Do: Upgrade immediately to Apache Syncope 4.0.8 or 4.1.3; note there is no fixed 3.0.x release, so 3.0.x deployments must move to a patched 4.x line. If immediate upgrade is not possible, restrict access to the Syncope admin console to trusted networks and VPN, enforce least-privilege on the database account Syncope uses, and review audit logs and database query history for anomalous entityKey or opEvent values containing SQL syntax indicating exploitation attempts. | 9.8 | — |
| nichelikely hundreds to low thousands of deployments worldwide (order of 10^2-10^3) |
Posted by Francesco Chicchiriccò on Sep 14 Severity: moderate Affected versions: - Apache Syncope (org.apache.syncope.core:syncope-core-persistence-jpa) 3.0.0-M0 through 3.0.16 - Apache Syncope (org.apache.syncope.core:syncope-core-persistence-jpa) 4.0.0-M0 through 4.0.7 - Apache Syncope (org.apache.syncope.core:syncope-core-persistence-jpa) 4.1.0-M0 through 4.1.2 Description: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability...
This source does not provide full text. Read it at seclists.org.