dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-49340

HIGH · 8.1 CVSS v3.1 Published 2026-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
gonic is a music streaming server / free-software subsonic server API implementation. Prior to version 0.21.0, a logic error in `ServeCreateOrUpdatePlaylist` allows any authenticated Subsonic user (including non-admin) to write playlist M3U content to an attacker-controlled absolute filesystem path on the gonic host, and to create intermediate directories with `0o777` permissions. The bug is independent of CVE-2026-49338 and CVE-2026-49339. It is an unreachable guard clause combined with no path containment in `Store.Write`. Version 0.21.0 patches the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A logic error in gonic's `ServeCreateOrUpdatePlaylist` function allows any authenticated Subsonic user to write playlist M3U content to an attacker-controlled absolute filesystem path. The vulnerability stems from an unreachable guard clause combined with missing path containment checks in `Store.Write`, enabling arbitrary file writes and creation of intermediate directories with 0o777 permissions.

MitigationUpgrade gonic to version 0.21.0 or later, which contains the patch addressing the path containment issue in the playlist handling code.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify gonic installation and version
    Check the gonic binary or service version using 'gonic --version', 'gonic -v', checking the executable file metadata, or reviewing the installed package version (e.g., via package manager)
    Affected if The installed version is lower than 0.21.0 (e.g., 0.20.0, 0.19.x, or earlier)
  2. Confirm Subsonic API is exposed
    Check if the gonic server is listening on its Subsonic API port (default 4747) by reviewing server configuration or running 'netstat -tlnp' or 'ss -tlnp' to find listening services
    Affected if The Subsonic API endpoint is accessible and accepting connections
  3. Verify Subsonic authentication is enabled
    Review gonic configuration files for authentication settings, typically in a config.yaml or config.json file, or check if the server requires Subsonic API credentials for playlist endpoints
    Affected if Authentication is enabled but allows any valid Subsonic user to authenticate (default configuration)
  4. Check playlist write functionality
    Review gonic source code or documentation to confirm the ServeCreateOrUpdatePlaylist endpoint exists and is accessible via the Subsonic API at /rest/createPlaylist.view or similar
    Affected if The playlist creation/update endpoint is available and responds to authenticated requests

A user is affected if running gonic version lower than 0.21.0 with the Subsonic API exposed and accessible to authenticated users, allowing them to write playlist content to arbitrary filesystem paths.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade gonic to version 0.21.0 or later, which contains the patch addressing the path containment issue in the playlist handling code.

Recommended fix High confidence

0.21.0

  1. 1. Identify the current gonic version installed (e.g., check via binary version flag or package manager)
  2. 2. Download gonic version 0.21.0 from the official GitHub repository releases
  3. 3. Replace the existing gonic binary with version 0.21.0
  4. 4. Restart the gonic service to load the updated binary
  5. 5. Verify the upgrade was successful by checking the version number

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49340 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49340 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data