CVE-2026-58271

published 21 Sep 2026 · updated 24 Sep 2026

@sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register`

6.8MediumCVSS 6.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

Sync-in Server is an open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.4.0, `POST /api/app/sync/register` accepts credentials and a TOTP code to register a desktop sync client. On a failed TOTP, `SyncClientsManager.register()` calls `updateAccesses(user, ip, false)`, which hits a freeze branch that writes `passwordAttempts` back unchanged. The counter never reaches `USER_MAX_PASSWORD_ATTEMPTS` (10) and the lockout gate never fires. A successful guess returns a `{clientId, clientToken}` pair. The token can be exchanged via `POST /api/app/sync/auth/cookie` for a full JWT. While the code is valid, the attacker can also call `POST /api/auth/2fa/disable` to permanently remove MFA. Version 2.4.0 patches the issue.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Sync-in<2.4.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-58271 severity on Zeptric[![CVE-2026-58271](https://zeptric.io/badge/cve/CVE-2026-58271.svg)](https://zeptric.io/cve/CVE-2026-58271)