ZeroHour
oss-securitypublished ()ingested 1

CVE-2026-78336: Apache Syncope: OIDCC4UI provider list discloses client secrets to any authenticated user

mediumVulnerabilityimportance 22CVE-2026-78336
AI summary · glm-5.3

Apache Syncope's OIDCC4UI extension leaks OIDC client secrets in the provider list to any authenticated user, versions through 4.1.2 affected.

CVE-2026-78336 is a moderate-severity insertion-of-sensitive-information-into-sent-data flaw in Apache Syncope's syncope-ext-oidcc4ui-logic module. The OIDCC4UI provider list discloses client secrets to any authenticated user. 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.

  • OIDC client secrets exposed via provider list endpoint
  • Any authenticated Syncope user can retrieve the secrets
  • Affects 3.0.x, 4.0.x, and 4.1.x through 4.1.2

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2026-78336
OIDC Client Secret Disclosure to Any Authenticated User in Apache Syncope

Apache Syncope contains an information disclosure flaw (CWE-201) in which any authenticated user — regardless of their entitlements or administrative privileges — can query the list of OIDC providers configured for single sign-on with the Console and Enduser UIs. The API response returns the full provider configuration, including OIDC client secrets, which should be restricted to administrators. An attacker with even a low-privileged account can harvest these secrets and potentially impersonate the Syncope deployment against the external identity providers, enabling token theft, unauthorized authentication, or lateral access to federated systems. Affected deployments span 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; the issue is fixed in 4.0.8 and 4.1.3. No CVSS score has been assigned yet, and no public proof of concept or in-the-wild exploitation is known.

Do: Upgrade immediately to Apache Syncope 4.0.8 or 4.1.3; note that no fixed 3.0.x release exists, so 3.0.16-and-earlier users must upgrade to 4.0.8 or 4.1.3. Regardless of upgrade timing, rotate the client secrets for every OIDC provider configured in the deployment, since any authenticated user could have already retrieved them. Also review Console/Enduser and REST API logs for provider-list queries from low-privileged accounts, and restrict network access to the Console and Enduser endpoints until patched.

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
moderate≈1,000–10,000 self-hosted deployments worldwide, most internal; internet-exposed Consoles likely in the low thousands at most
Full article

Posted by Francesco Chicchiriccò on Sep 14 Severity: moderate Affected versions: - Apache Syncope (org.apache.syncope.ext.oidcc4ui:syncope-ext-oidcc4ui-logic) 3.0.0-M0 through 3.0.16 - Apache Syncope (org.apache.syncope.ext.oidcc4ui:syncope-ext-oidcc4ui-logic) 4.0.0-M0 through 4.0.7 - Apache Syncope (org.apache.syncope.ext.oidcc4ui:syncope-ext-oidcc4ui-logic) 4.1.0-M0 through 4.1.2 Description: Insertion of sensitive information into sent data vulnerability in Apache Syncope. Any...

This source does not provide full text. Read it at seclists.org.