ZeroHour
Story · 1 source · 3 articlesfirst updated ()

Apache Syncope discloses three cross-Realm authorization vulnerabilities: CVE-2026-73236, CVE-2026-73370, and CVE-2026-73668

What's new: A new report adds CVE-2026-73668, a third moderate-rated incorrect-authorization vulnerability in which administrators can read confidential ConnId bundle configuration values from realms outside their entitlements, expanding the story from two to three same-day Syncope disclosures sharing identical affected version ranges.
Merged summary · glm-5.3 · rewritten as coverage arrives

Three incorrect-authorization flaws in Apache Syncope's delegated administration let users cross Realm boundaries: a prefix-matching bypass (important), a reconciliation bypass (moderate), and disclosure of confidential ConnId bundle configuration values from…

On 2026-09-14, the Apache Syncope project disclosed three related incorrect authorization vulnerabilities in its delegated administration feature, all affecting the same version ranges: Syncope 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. CVE-2026-73236, rated important, arises because delegated administration checks are enforced via Realm hierarchy prefix matches: two sibling Realms whose names begin with the same string cannot be correctly distinguished, allowing delegated administrators to act outside their assigned Realm. CVE-2026-73370, rated moderate and residing in the syncope-core-idm-logic module, allows reconciliation actions to bypass cross-Realm delegated administration security checks. CVE-2026-73668, also rated moderate and affecting syncope-core-idm-logic, allows an administrator with entitlements in one realm to view confidential ConnId bundle configuration values belonging to other realms. The recommended remediation for all three issues is upgrading to the latest fixed releases; the disclosures do not state specific fixed version numbers.

  • CVE-2026-73236: important-rated incorrect authorization flaw; Realm hierarchy prefix matching cannot distinguish sibling Realms sharing a name prefix, letting delegated admins act outside their assigned Realm
  • CVE-2026-73370: moderate-rated incorrect authorization flaw in syncope-core-idm-logic; reconciliation actions can bypass cross-Realm delegated administration security checks
  • CVE-2026-73668: moderate-rated incorrect authorization flaw in syncope-core-idm-logic; administrators with entitlements in one realm can view confidential ConnId bundle configuration values of other realms
  • All three CVEs affect Syncope 3.0.0-M0–3.0.16, 4.0.0-M0–4.0.7, and 4.1.0-M0–4.1.2
  • Remediation for all three is upgrading to the latest fixed releases; no specific fixed version numbers were stated in the disclosures
  • All three disclosed via oss-security on 2026-09-14

Coverage timeline

  1. · 1d ago
    oss-security· 28
    CVE-2026-73236: Apache Syncope: Cross-Realm authorization bypass in delegated administration

    Apache Syncope CVE-2026-73236 bypasses delegated administration checks for sibling Realms sharing a name prefix.

  2. · 1d ago
    oss-security· 20
    CVE-2026-73370: Apache Syncope: Cross-Realm boundaries reconciliation bypass

    Apache Syncope CVE-2026-73370 allows reconciliation actions to bypass cross-Realm delegated administration boundaries.

  3. · 1d ago
    oss-security· 18
    CVE-2026-73668: Apache Syncope: Cross-realm disclosure of confidential ConnId bundles configuration values

    Apache Syncope cross-realm authorization flaw lets administrators read confidential ConnId bundle configuration values from realms they should not access (CVE-2026-73668).

Vulnerabilities in this storyAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2026-73236
Cross-Realm Authorization Bypass in Apache Syncope Delegated Administration

Apache Syncope, an open-source identity management platform, enforces delegated administration entitlements by checking whether a target object's Realm sits under an administrator's assigned Realm, using prefix matches on realm names. Due to an incorrect implementation (CWE-863), two sibling Realms whose names begin with the same string cannot be distinguished, so a delegated administrator for one Realm can effectively act on objects in the other Realm. An authenticated attacker holding delegated-administrator rights over one realm gains unauthorized access to users, groups, and other managed objects in the sibling realm — a horizontal privilege escalation between administrative domains. Affected deployments are Apache Syncope 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; fixes ship in 4.0.8 and 4.1.3, with no patched 3.0.x release listed. No public proof of concept is known, the issue is not in CISA's KEV, and there is no indication of exploitation in the wild.

Do: Upgrade to Apache Syncope 4.0.8 or 4.1.3 as soon as possible; 3.0.x has no fixed release, so deployments on that line must migrate to a patched 4.x version. Until patched, avoid sibling Realm names that share a leading string and review delegated-administration assignments for realms whose names could collide. Audit Syncope logs for delegated administrators performing operations on realms outside their assigned scope.

7.5
  • Apache Syncope 3.0.0-M0 through 3.0.16
  • Apache Syncope 4.0.0-M0 through 4.0.7
  • Apache Syncope 4.1.0-M0 through 4.1.2
nichelikely hundreds to low thousands of self-hosted deployments worldwide (order-of-magnitude estimate)
CVE-2026-73370
Broken Authorization in Apache Syncope Reconciliation Bypasses Delegated-Admin Entitlements

Apache Syncope, an open-source identity management (IdM) platform, contains an incorrect authorization flaw (CWE-863) in the Reconciliation service: the delegated-administration security checks applied to its pull and push operations are incomplete. As a result, an administrator account that was never granted the required entitlements can still invoke reconciliation pull and push actions, which synchronize identities across realms and connected resources — enabling reconciliation to be triggered across realm boundaries beyond that admin's delegated scope. This can let an under-privileged or rogue delegated administrator read or alter identity data (users, groups, accounts on connected systems) outside the realm they administer. 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; fixes are available in 4.0.8 and 4.1.3, with no fixed 3.0.x release listed. The issue has no CVSS score yet, is not in the CISA KEV catalog, and there is no known public PoC or evidence of in-the-wild exploitation.

Do: Upgrade immediately to Apache Syncope 4.0.8 or 4.1.3; organizations still on the 3.0.x line must upgrade to a fixed 4.x release since no 3.0 fix was published. Restrict access to the Reconciliation service (pull/push) so only fully entitled administrators can invoke it, and audit logs for pull/push executions initiated by delegated administrators who lacked the corresponding entitlements. Investigate any resulting cross-realm identity changes or unexpected synchronizations to connected resources.

9.8
  • Apache Syncope
nicheunknown exact count; plausibly hundreds to low thousands of self-hosted enterprise IdM deployments
CVE-2026-73668
Cross-Realm Confidential Connector Config Disclosure in Apache Syncope

Apache Syncope, an open-source identity and access management (IdM) platform, contains an incorrect authorization flaw (CWE-863) in its REST API that lets an authenticated administrator who has full entitlements in one Realm read the complete Connector configuration scoped to a different Realm — including confidential properties such as the credentials used to bind to connected external resources (e.g., LDAP/AD, databases) via ConnId connector bundles. The attacker gains those secrets and can effectively clone the Connector instance into their own Realm, giving them working credentials for the target Realm's backend systems and enabling lateral movement outside their delegated administrative scope. The issue affects Syncope 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; it is fixed in 4.0.8 and 4.1.3 (the 3.0.x line has no listed fix, so those users must upgrade to a fixed 4.x release). Exploitation requires an already-privileged internal account, so the risk is primarily privilege escalation across realm boundaries by semi-trusted or compromised tenant administrators. No CVSS score has been assigned, it is not in the CISA KEV catalog, and no public proof of concept or known in-the-wild exploitation exists.

Do: Upgrade Apache Syncope to 4.0.8 or 4.1.3; deployments still on the 3.0.x line (up to 3.0.16) have no fixed 3.0.x release and should migrate to a fixed 4.x version. Until patched, minimize the number of realm-scoped administrators, review REST access logs for any admin reading Connector configurations outside their own Realm, and rotate the credentials stored in Connector confidential properties (e.g., LDAP/AD and database bind accounts) since they may have been readable cross-realm.

9.8
  • Apache Syncope 3.0.0-M0 through 3.0.16
  • Apache Syncope 4.0.0-M0 through 4.0.7
  • Apache Syncope 4.1.0-M0 through 4.1.2
nicheunknown exact count; likely low thousands of self-hosted enterprise instances at most