CVE-2026-87802: Apache Syncope: SRA OAuth2 JWT signature verification bypass
Low-severity CVE-2026-87802 in Apache Syncope SRA allows JWT signature forgery in OAuth 2.0 setups without JWKS URI.
CVE-2026-87802 is a low-severity improper cryptographic signature verification flaw in Apache Syncope SRA affecting 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. When SRA is configured for OAuth 2.0 without a JWKS set URI assigned, an attacker can forge tokens, bypassing JWT signature verification.
- JWT signature verification bypass when JWKS URI is not configured
- Affects Syncope SRA 3.0.x, 4.0.x, and 4.1.x milestone/release lines
- Rated low severity by upstream maintainer
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-87802 | JWT signature verification bypass in Apache Syncope SRA OAuth 2.0 gateway Apache Syncope contains an improper verification of cryptographic signatures (CWE-347) in its SRA gateway when the gateway is configured for OAuth 2.0 without a JWKS URI assigned. Under that configuration the gateway fails to properly validate JWT signatures, so an attacker who can reach the SRA can forge arbitrary JWTs claiming any user identity and permissions, gaining full access to the services proxied by the SRA. Affected deployments run Apache Syncope 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.7, or 4.1.0-M0 through 4.1.2 with the optional SRA gateway in this configuration; core Syncope deployments not using the SRA are not directly exposed. There is no public proof of concept, no known exploitation, the issue is not in the CISA KEV catalog, and a CVSS score has not yet been assigned. Do: Upgrade Apache Syncope to 4.0.8 or 4.1.3; the 3.0.x line has no listed fix, so 3.0.x users should move to a fixed 4.x release. If immediate upgrade is not possible, ensure the SRA's OAuth 2.0 / OIDC configuration has a valid JWKS URI assigned, since the flaw only manifests when no JWKS URI is set. Review SRA and backend service logs for tokens with unexpected subjects, issuers, or privilege levels that could indicate forged JWTs. | 9.1 | — |
| niche |
Posted by Francesco Chicchiriccò on Sep 14 Severity: low Affected versions: - Apache Syncope (org.apache.syncope:syncope-sra) 3.0.0-M0 through 3.0.16 - Apache Syncope (org.apache.syncope:syncope-sra) 4.0.0-M0 through 4.0.7 - Apache Syncope (org.apache.syncope:syncope-sra) 4.1.0-M0 through 4.1.2 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...
This source does not provide full text. Read it at seclists.org.