@sync-in/server vulnerabilities

Browse known CVEs and advisories by package and ecosystem. Severity tells you the worst case. What determines real risk is whether the vulnerable code actually runs in your applications.

Get a demo

Browse by ecosystem

npmPyPIMavenGoRubyGemsCargoNuGetComposerpubSwiftGitHub Actions
CVE-IDSeverityPackage summary
CVE-2026-58272Medium@sync-in/server: Sync-in Server has Username/Login Enumeration via Timing Side-Channel on POST /api/auth/login (incomplete fix of the prior timing-attack…CVE-2026-58270Medium@sync-in/server: Sync-in Server has a ReDoS via Unsanitized Regex in Sync Diff `pathFilters`CVE-2026-58269High@sync-in/server: Sync-in Server has a complete 2FA Bypass via `POST /api/auth/token`CVE-2026-58271Medium@sync-in/server: @sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register`CVE-2026-47684High@sync-in/server: Sync-in Server: SSRF protection bypass via IPv4-mapped IPv6 addresses in regExpPrivateIPCVE-2026-41161Medium@sync-in/server: Sync-in Server has Username Enumeration via Timing AttackCVE-2025-67438Medium@sync-in/server: Sync-in Server has a stored cross-site scripting (XSS) vulnerability

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo