{"answers":{"affected":"2 open source packages ship an affected version, including @sync-in/server.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58272 exists.","fix":"Upgrade @sync-in/server to 2.4.1 or later.","what":"CVE-2026-58272 is a medium-severity vulnerability in Sync-in server, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-58272 and fix it if it is affected.\n\nWhat it is: CVE-2026-58272 is a medium-severity vulnerability in Sync-in server, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58272 exists.\n\nAffected packages and fixed versions:\n- @sync-in/server (npm): affected all versions; fixed in 2.4.1\n- @sync-in/server (npm): affected all versions; fixed in 2.4.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-58272/ (Markdown: https://insights.sbomify.com/CVE-2026-58272/index.md)","id":"CVE-2026-58272","markdown":"https://insights.sbomify.com/CVE-2026-58272/index.md","name":"CVE-2026-58272","record":{"aliases":["GHSA-29hq-23m2-2j47"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Sync-in Server","requires_auth":"none","summary":"An unauthenticated attacker can enumerate valid usernames via timing side-channels in the login endpoint, facilitating credential stuffing and phishing attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Sync-in Server has Username/Login Enumeration via Timing Side-Channel on POST /api/auth/login (incomplete fix of the prior timing-attack advisory)","id":"CVE-2026-58272","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Azure DNS Elevation of Privilege Vulnerability","id":"CVE-2026-58275"},"packages":[{"ecosystem":"npm","fixed":["2.4.1"],"introduced":["0"],"last_affected":[],"package":"@sync-in/server","purl":null,"source":"GHSA-29hq-23m2-2j47"},{"ecosystem":"npm","fixed":["2.4.1"],"introduced":["0"],"last_affected":[],"package":"@sync-in/server","purl":"pkg:npm/%40sync-in/server","source":"GHSA-29hq-23m2-2j47"}],"prev":{"headline":"@sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register`","id":"CVE-2026-58271"},"products":["server"],"published":"2026-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-23","vendors":["Sync-in"]},"summary":"An unauthenticated attacker can enumerate valid usernames via timing side-channels in the login endpoint, facilitating credential stuffing and phishing attacks.","url":"https://insights.sbomify.com/CVE-2026-58272/"}