Skip to main content

CVE-2026-58272: CWE-208: Observable Timing Discrepancy in Sync-in server

0
Medium
VulnerabilityCVE-2026-58272cvecve-2026-58272cwe-208
Published: 09/21/2026 (09/21/2026, 20:31:46 UTC)
Source: CVE Database V5
Vendor/Project: Sync-in
Product: server

Description

Sync-in Server is an open-source platform for file storage, sharing, collaboration, and syncing. Versions prior to 2.4.1 contain an observable timing discrepancy in the login endpoint because authentication attempts for nonexistent accounts return without performing the bcrypt comparison used for existing accounts. An unauthenticated attacker can measure response times to enumerate valid usernames or email addresses, facilitating credential-stuffing, password-spraying, and phishing attacks. Version 2.4.1 contains a patch.

CVSS v3.1

Score 5.3medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected software

Sync-in

server

Affected versions
<2.4.1
GitHub Actionsmore threats →ai
sync-in/server
pkg:github/sync-in/server
Affected versions
<2.4.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/21/2026, 21:01:52 UTC

Technical Analysis

CVE-2026-58272 describes a timing discrepancy vulnerability in Sync-in Server's login endpoint affecting versions before 2.4.1. The flaw arises because the server returns responses for nonexistent accounts faster than for existing accounts due to skipping bcrypt password hash comparisons. This timing difference allows unauthenticated attackers to enumerate valid user identifiers by measuring response times. The vulnerability is classified under CWE-208 (Observable Timing Discrepancy). The issue is fixed in version 2.4.1.

Potential Impact

The vulnerability enables unauthenticated attackers to enumerate valid usernames or email addresses by observing response time differences during login attempts. This information disclosure can facilitate targeted credential-stuffing, password-spraying, and phishing attacks. The confidentiality impact is low, with no direct impact on integrity or availability reported.

Mitigation Recommendations

Upgrade Sync-in Server to version 2.4.1 or later, which contains an official patch addressing the timing discrepancy vulnerability. No additional mitigation is required once the patch is applied.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-06-29T21:54:30.332Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ab197cf55bf5e2cf5736874

Added to database: 09/21/2026, 20:47:11 UTC

Last enriched: 09/21/2026, 21:01:52 UTC

Last updated: 09/21/2026, 22:11:59 UTC

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses