---
id: CVE-2026-73668
title: >-
  Incorrect Authorization vulnerability in Apache Syncope.






  An administrator with adequate entitlements in a given Realm may be able to
  read via REST the full Connector configuration, confidential properties
  included, scoped in another…
summary: >-
  Incorrect Authorization vulnerability in Apache Syncope.






  An administrator with adequate entitlements in a given Realm may be able to
  read via REST the full Connector configuration, confidential properties
  included, scoped in another…
severity: critical
cvss: 9.8
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-863
vendor: Apache Software Foundation
product: 'org.apache.syncope.core.idm:syncope-core-idm-logic'
affected:
  - 'org.apache.syncope.core.idm:syncope-core-idm-logic >= 3.0.0-M0 <= 3.0.16'
  - 'org.apache.syncope.core.idm:syncope-core-idm-logic >= 4.0.0-M0 <= 4.0.7'
  - 'org.apache.syncope.core.idm:syncope-core-idm-logic >= 4.1.0-M0 <= 4.1.2'
published: '2026-09-14'
updated: '2026-09-14'
sourceUpdated: '2026-09-14T20:58:48.430'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-73668'
references:
  - url: 'https://lists.apache.org/thread/4lgsbbgc72mngf6mc1q5b1cj3d9nyphn'
    label: security@apache.org
  - url: 'http://www.openwall.com/lists/oss-security/2026/09/14/11'
    label: af854a3a-2127-422b-91ae-364da2661108
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: total
  timestamp: '2026-09-14T19:14:03.871601Z'
ingestedAt: '2026-09-14T15:23:07.430Z'
epss: 0.00477
epssPercentile: 0.40365
---

## Overview

Incorrect Authorization vulnerability in Apache Syncope.





An administrator with adequate entitlements in a given Realm may be able to read via REST the full Connector configuration, confidential properties included, scoped in another Realm and thus be able to effectively duplicate such Connector instance into the Realm they have administration rights for.

This issue affects Apache Syncope: from 3.0.0-M0 through 3.0.16, from 4.0.0-M0 Through 4.0.7, from 4.1.0-M0 through 4.1.2.


Users are recommended to upgrade to version 4.0.8 / 4.1.3, which fix this issue.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.