← Back
CVE-2026-49339
high
CVSS 7.1
Path Traversal in go.senan.xyz/gonic (CVE-2026-49339)
Summary
path traversal in go.senan.xyz/gonic (CVE-2026-49339). Data can be tampered with by attackers. Exploitable via ``playlist.UserID``. Mitigation: upgrade to `0.21.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-49339** has been found in go.senan.xyz/gonic.
Attackers can target a specific entry point like ``playlist.UserID`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade go.senan.xyz/gonic to **0.21.0** or later.
If unsure, ask your IT team or search "go.senan.xyz/gonic CVE-2026-49339" on the vendor's site.
CVE-2026-49339 (go.senan.xyz/gonic) — CWE-22 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `playlist.UserID` / `deletePlaylist` / `userIDFromPath` / `strconv.Atoi`
Patched: `0.21.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.
❓ What is the problem
**Path traversal** (CWE-22) exists in go.senan.xyz/gonic. Attackers reach the vulnerable code path via ``playlist.UserID`` without authentication.
📍 Affected scope
go.senan.xyz/gonic — . Attack surface: `playlist.UserID` / `deletePlaylist` / `userIDFromPath` / `strconv.Atoi`.
🔥 Severity
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers
🔧 How to fix
Update to **0.21.0**.
🛡️ 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 'go.senan.xyz/gonic' .` 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 'go.senan.xyz/gonic' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `go.senan.xyz/gonic` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade go.senan.xyz/gonic to 0.21.0ステージング環境で 0.21.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
go.senan.xyz/gonic
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.21.0"}]}]
References
- web https://github.com/sentriz/gonic/commit/0824bed88f6bbc490ba28bf09d28e5dfeb07b445
- web https://github.com/sentriz/gonic/commit/6dd71e6
- web https://github.com/sentriz/gonic/security/advisories/GHSA-2fp4-5v5c-4448
- web https://nvd.nist.gov/vuln/detail/CVE-2026-49339
- web https://github.com/advisories/GHSA-2fp4-5v5c-4448