Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-87802 – Authentication Bypass via JWT Forgery – Apache Syncope SRA 3.0.0-M0 through 4.1.2

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-87802 is an improper verification of cryptographic signature vulnerability (CWE-347) affecting the Secure Remote Access (SRA) component of Apache Syncope. When SRA is configured to use OAuth 2.0 without a JWKS set URI assigned, a remote unauthenticated attacker can forge arbitrary JSON Web Tokens (JWTs) and impersonate any user identity, gaining full access to services proxied by SRA. The flaw carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: SRA’s OAuth 2.0 token validation logic does not enforce signature verification when the JWKS (JSON Web Key Set) URI is not explicitly configured, allowing a JWT with an arbitrary or unsigned/self-signed signature to be accepted as valid.
  • Trigger conditions: Exploitation requires SRA to be deployed with OAuth 2.0 authentication enabled while the JWKS set URI configuration option has been left unset.
  • Attack vector: Network-based, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N). An attacker crafts a JWT asserting any username, role, or claim and presents it to SRA.
  • Impact: Because SRA accepts the forged token, the attacker can impersonate arbitrary users — including administrators — and obtain unauthorized access to any backend service proxied through SRA. This yields high confidentiality and integrity impact; availability is not affected.

Affected software

  • Apache Syncope (org.apache.syncope:syncope-sra), when SRA is configured for OAuth 2.0 without a JWKS set URI:
    • 3.0.0-M0 through 3.0.16
    • 4.0.0-M0 through 4.0.7
    • 4.1.0-M0 through 4.1.2

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Apache Syncope to version 4.0.8 or 4.1.3, both of which fix this issue.
  • If immediate patching is not possible: Ensure any SRA deployment using OAuth 2.0 has a valid JWKS set URI explicitly configured so that JWT signatures are properly verified. Deployments without OAuth 2.0 enabled on SRA, or with a correctly configured JWKS URI, are not affected. Restrict network exposure of SRA-proxied services until patched.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge