← Back
CVE-2026-53553
Path Traversal in github.com/zhenorzz/goploy (CVE-2026-53553)
Summary
path traversal in github.com/zhenorzz/goploy (CVE-2026-53553). Risk of unauthorized operations or information disclosure. Exploitable via ``filePath``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-53553** has been found in github.com/zhenorzz/goploy.
Attackers can target a specific entry point like ``filePath`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/zhenorzz/goploy CVE-2026-53553" on the vendor's site.
CVE-2026-53553 (github.com/zhenorzz/goploy) — CWE-22 /
Attack surface: `filePath` / `os.ReadFile` / `srcText` / `serverID`
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.
❓ What is the problem
**Path traversal** (CWE-22) exists in github.com/zhenorzz/goploy. Attackers reach the vulnerable code path via ``filePath`` without authentication.
📍 Affected scope
github.com/zhenorzz/goploy — . Attack surface: `filePath` / `os.ReadFile` / `srcText` / `serverID`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/zhenorzz/goploy' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/zhenorzz/goploy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/zhenorzz/goploy` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/zhenorzz/goploy
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]