CVE-2026-58269
Sync-in Server is an open-source platform for file storage, …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/Sync-in/server/security/advisories/GHSA-92cr-jxw4-5wjg
- nvd.nist.gov/vuln/detail/CVE-2026-58269
- github.com/Sync-in/server/pull/228
- github.com/Sync-in/server/commit/3ec74e2ea1f538fe1a3ac9487bdf24a19e548361
- github.com/Sync-in/server/releases/tag/v2.4.0
- github.com/advisories/GHSA-92cr-jxw4-5wjg
- nvd.nist.gov/vuln/detail/CVE-2026-58269
- cve.org/CVERecord?id=CVE-2026-58269
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.