CVE-2026-58269
Sync-in Server has a complete 2FA Bypass via `POST /api/auth/token`
- High 8.1
Description
Sync-in Server is an open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.4.0, `POST /api/auth/token` authenticates with username and password only, then calls `getTokens()`, which returns full access and refresh JWTs without checking whether the account has TOTP 2FA enabled. An attacker with stolen or phished credentials can bypass 2FA in a single request. The parallel login endpoint (`POST /api/auth/login`) correctly enforces 2FA by calling `setCookies(user, res, true)`, which gates on `user.twoFaEnabled`. Version 2.4.0 patches the issue.
Key facts
- Published
- 21 Sep 2026
- Last changed
- 24 Sep 2026
- Assigned by
- GitHub_M
- EPSS
- 0.274% likely to be exploited in the next 30 days, higher than 20.026% of CVEs (scores for 16 Nov 2026)
- SSVC (CISA)
- Exploitation: poc; Automatable: no; Technical impact: total
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 8.1CVSS 3.1, Highfrom the CNA (GitHub_M)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Sync-in | server |
|
Timeline
- 21 Sep 2026 Published