Answer in brief
CVE-2026-58269 records a High severity (CVSS 8.1) vulnerability in Sync-in Server has a complete 2FA Bypass via `POST /api/auth/token`. The current sources do not mark it as known exploited. The current feed maps Sync-in/server (generic), @sync-in/server (npm), @sync-in/server (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Sync-in/server (generic), @sync-in/server (npm), @sync-in/server (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Sync-in/servergeneric | <2.4.0 | 2.4.0 |
| @sync-in/servernpm | >=0 <2.4.0 | 2.4.0 |
| @sync-in/servernpm | <=2.3.0 | 2.4.0 |
Published upstream
Sep 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.