{"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-47684 exists.","fix":"Upgrade @sync-in/server to 2.3.0 or later.","what":"CVE-2026-47684 is a high-severity server-side request forgery vulnerability in Sync-in server, published on 16 Jun 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-47684 and fix it if it is affected.\n\nWhat it is: CVE-2026-47684 is a high-severity server-side request forgery vulnerability in Sync-in server, published on 16 Jun 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-47684 exists.\n\nAffected packages and fixed versions:\n- @sync-in/server (npm): affected all versions; fixed in 2.3.0\n- @sync-in/server (npm): affected all versions; fixed in 2.3.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-47684/ (Markdown: https://insights.sbomify.com/CVE-2026-47684/index.md)","id":"CVE-2026-47684","markdown":"https://insights.sbomify.com/CVE-2026-47684/index.md","name":"CVE-2026-47684","record":{"aliases":["GHSA-q4x5-8cj6-52wg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Sync-in Server","requires_auth":"low_privilege","summary":"Attackers can bypass SSRF protections in Sync-in Server by using IPv4-mapped IPv6 addresses to access internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Sync-in Server is a secure, open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.3.0, the private IP blocklist regex used in the URL download feature does not match IPv4-mapped IPv6 addresses (e.g. ::ffff:127.0.0.1), allowing SSRF protection to be bypassed on dual-stack systems. Version 2.3.0 fixes 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: SSRF protection bypass via IPv4-mapped IPv6 addresses in regExpPrivateIP","id":"CVE-2026-47684","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"FOGProject has stored XSS via unauthenticated inventory service renders unescaped in Host Management page","id":"CVE-2026-47685"},"packages":[{"ecosystem":"npm","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"@sync-in/server","purl":null,"source":"GHSA-q4x5-8cj6-52wg"},{"ecosystem":"npm","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"@sync-in/server","purl":"pkg:npm/%40sync-in/server","source":"GHSA-q4x5-8cj6-52wg"}],"prev":{"headline":"vm2: bufferAllocLimit cap bypassed by Buffer.concat and Buffer.from arrayLike","id":"CVE-2026-47683"},"products":["server"],"published":"2026-06-16","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-06-16","vendors":["Sync-in"]},"summary":"Attackers can bypass SSRF protections in Sync-in Server by using IPv4-mapped IPv6 addresses to access internal resources.","url":"https://insights.sbomify.com/CVE-2026-47684/"}