{"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-58270 exists.","fix":"Upgrade @sync-in/server to 2.4.0 or later.","what":"CVE-2026-58270 is a medium-severity denial of service vulnerability in Sync-in server, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-58270 and fix it if it is affected.\n\nWhat it is: CVE-2026-58270 is a medium-severity denial of service vulnerability in Sync-in server, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58270 exists.\n\nAffected packages and fixed versions:\n- @sync-in/server (npm): affected all versions; fixed in 2.4.0\n- @sync-in/server (npm): affected all versions; fixed in 2.4.0\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-58270/ (Markdown: https://insights.sbomify.com/CVE-2026-58270/index.md)","id":"CVE-2026-58270","markdown":"https://insights.sbomify.com/CVE-2026-58270/index.md","name":"CVE-2026-58270","record":{"aliases":["GHSA-jx63-h26r-8cph"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Sync-in Server","requires_auth":"low_privilege","summary":"Attackers can cause a denial of service in Sync-in Server by submitting malicious regex patterns that block the event loop.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1333","name":"Inefficient Regular Expression Complexity"}],"description":"Sync-in Server is an open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.4.0, the sync diff endpoint compiles a user-supplied string into a `RegExp` with no complexity validation. A catastrophic-backtracking pattern (e.g. `^(a+)+b`) blocks the Node.js event loop, making the entire server unresponsive to all users until the container is restarted. Version 2.4.0 patches the issue.","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 a ReDoS via Unsanitized Regex in Sync Diff `pathFilters`","id":"CVE-2026-58270","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"@sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register`","id":"CVE-2026-58271"},"packages":[{"ecosystem":"npm","fixed":["2.4.0"],"introduced":["0"],"last_affected":[],"package":"@sync-in/server","purl":null,"source":"GHSA-jx63-h26r-8cph"},{"ecosystem":"npm","fixed":["2.4.0"],"introduced":["0"],"last_affected":[],"package":"@sync-in/server","purl":"pkg:npm/%40sync-in/server","source":"GHSA-jx63-h26r-8cph"}],"prev":{"headline":"Sync-in Server has a complete 2FA Bypass via `POST /api/auth/token`","id":"CVE-2026-58269"},"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["Sync-in"]},"summary":"Attackers can cause a denial of service in Sync-in Server by submitting malicious regex patterns that block the event loop.","url":"https://insights.sbomify.com/CVE-2026-58270/"}