SSRF (Server-Side Request Forgery) in @sync-in/server (CVE-2026-47684)
Summary
SSRF in @sync-in/server (CVE-2026-47684). Confidential information can be exposed externally. Mitigation: upgrade to 2.3.0 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47684 has been found in @sync-in/server.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade @sync-in/server to 2.3.0 or later.
If unsure, ask your IT team or search "@sync-in/server CVE-2026-47684" on the vendor's site.
CVE-2026-47684 (@sync-in/server) — CWE-918 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in @sync-in/server.
Check the vendor advisory for the affected versions of @sync-in/server.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 2.3.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@sync-in/server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@sync-in/server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@sync-in/serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @sync-in/server to 2.3.0ステージング環境で 2.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com