CVE-2026-87802

Apache Syncope: SRA OAuth2 JWT signature verification bypass

Published Sep 14, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
Improper verification of cryptographic signature vulnerability in Apache Syncope.



When SRA is configured for OAuth 2.0 without JWKS set URI assigned, an attacker can forge arbitrary JWTs to impersonate any user identity and permissions, gaining full access to services proxied by SRA.

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.

Analysis

AI-generated

Technical impact

Improper verification of cryptographic signatures in Apache Syncope’s Service Resource Adapter (SRA) when configured for OAuth 2.0 without a JWKS set URI allows an attacker to forge JSON Web Tokens (JWTs). The forged tokens can impersonate any user identity and grant the attacker the same permissions that the legitimate user would have, effectively bypassing authentication. This weakness is identified as CWE‑347 and creates a critical authentication bypass that can lead to full control over services proxied by SRA.

Affected Systems

Apache Syncope versions 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 are affected. These ranges include all milestone and initial release builds of the 3.x, 4.0.x, and 4.1.x series. The issue does not appear in versions prior to 3.0.0‑M0 or in 4.0.8 and later, 4.1.3 and later.

Risk and Exploitability

Because the flaw allows an unauthenticated attacker to create a valid JWT when SRA is misconfigured, the risk is high and the potential impact includes unauthorized full access to all services protected by SRA. No EPSS score is available, and the vulnerability is not listed in the CISA KEV catalog. Attackers need only access to the OAuth 2.0 configuration or the service endpoint to craft a malicious token; no additional privileges or local access are required. Given the severity and the lack of known mitigation until patching, administrators should treat this as a high‑risk issue and prioritize remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Syncope to version 4.0.8 or 4.1.3 or later, which resolves the signature verification flaw.
  • Verify that the SRA OAuth 2.0 configuration includes a valid JWKS set URI so that JWT signatures are strictly verified.
  • Restrict exposure of SRA endpoints to trusted networks or users until the upgrade is applied, limiting an attacker’s ability to use forged tokens.

Generated by OpenCVE AI on September 15, 2026 at 14:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
References
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache syncope
Vendors & Products Apache
Apache syncope
Type Values Removed Values Added
Description Improper verification of cryptographic signature vulnerability in Apache Syncope. When SRA is configured for OAuth 2.0 without JWKS set URI assigned, an attacker can forge arbitrary JWTs to impersonate any user identity and permissions, gaining full access to services proxied by SRA. 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.
Title Apache Syncope: SRA OAuth2 JWT signature verification bypass
Weaknesses CWE-347
References
Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Sep 14, 2026, 7:39 PM
Reserved
Sep 9, 2026, 10:11 AM
Status
Deferred
Published
Sep 14, 2026, 11:17 AM
Modified
Sep 14, 2026, 8:58 PM