CVE-2026-58271 json
@sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register`
published last mo. modified last mo. also EUVD-2026-84112 , GHSA-274f-6w77-8qm9
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm @sync-in/server 2.4.0
- sync-in sync-in_server 2.4.0
- github.com/Sync-in/server@b13a4aa commit
- github.com/Sync-in/server#228 pull request
- github.com/Sync-in/server/releases/tag/v2.4.0 release
Is CVE-2026-58271 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last mo.
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/Sync-in/server/security/advisories/GHSA-274f-6w77-8qm9 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @sync-in/server | <2.4.0 |
2.4.0 |
Affected products
- Sync-in server
Classification
- Weakness
-
- CWE-307 Improper Restriction of Excessive Authentication Attempts
References
-
github.com
/Sync-in/server/pull/228
web
-
github.com
/Sync-in/server/commit/b13a4aad5c2b38fe8231a0d007cd08a086ec5bdb
web
-
github.com
/Sync-in/server/security/advisories/GHSA-274f-6w77-8qm9
exploit, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-58271
advisory
-
github.com
/Sync-in/server
package
-
github.com
/Sync-in/server/releases/tag/v2.4.0
web
Sources
- CVE List CVE-2026-58271
- GitHub Advisory GHSA-274f-6w77-8qm9
- NVD CVE-2026-58271
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.