# CVE-2026-49339: gonic: Path Traversal in playlist `id` bypasses ownership check, enabling any user to read/delete other users' playlists

> Authenticated users can bypass ownership checks via path traversal to read or delete other users' playlists and probe host files.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-2fp4-5v5c-4448, GO-2026-5825

## What is CVE-2026-49339?

CVE-2026-49339 is a high-severity path traversal vulnerability in sentriz gonic, published on 19 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

gonic is a music streaming server / free-software subsonic server API implementation. The maintainer's fix in  commit `6dd71e6a3c966867ef8c900d359a7df75789f410` added an ownership check based on `playlist.UserID`. However, `playlist.UserID` is derived from the first path segment of the attacker-controlled playlist ID, with no path containment on the resolved file path. Any authenticated Subsonic user can therefore bypass the ownership check and read any other user's playlist, delete any other user's playlist, and probe arbitrary file paths on the host for existence/readability. This is a bypass of the boundary the `6dd71e6` fix is trying to enforce; it is closely related to the original GONIC-1 IDOR but uses a different primitive (path traversal in the `id` parameter rather than direct cross-user access). Commit 0824bed88f6bbc490ba28bf09d28e5dfeb07b445 in version 0.21.0 fixes the issue.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-49339?

3 open source packages ship an affected version, including go.senan.xyz/gonic.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `go.senan.xyz/gonic` | Go | All versions | 0.21.0 |
| `go.senan.xyz/gonic` | Go | All versions | 0.21.0 |
| `go.senan.xyz/gonic` | Go | All versions | 0.21.0 |

## How do I fix CVE-2026-49339?

Upgrade go.senan.xyz/gonic to 0.21.0 or later.

## Is CVE-2026-49339 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49339 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49339 and fix it if it is affected.

What it is: CVE-2026-49339 is a high-severity path traversal vulnerability in sentriz gonic, published on 19 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49339 exists.

Affected packages and fixed versions:
- go.senan.xyz/gonic (Go): affected all versions; fixed in 0.21.0
- go.senan.xyz/gonic (Go): affected all versions; fixed in 0.21.0
- go.senan.xyz/gonic (Go): affected all versions; fixed in 0.21.0

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49339/ (Markdown: https://insights.sbomify.com/CVE-2026-49339/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49339
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49339
- OSV: https://osv.dev/vulnerability/CVE-2026-49339

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49339/
Summaries are generated and may contain mistakes; the official description above is the record.
