# CVE-2026-23877: Directory Traversal & Filesystem can be accessed by a non-admin user

> Authenticated non-admin users can browse arbitrary server directories via a directory traversal flaw in the folder browser endpoint.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA: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 Jan 2026
- **Updated:** 20 Jan 2026
- **Also known as:** GHSA-pj88-9xww-gxmh, PYSEC-2026-1947

## What is CVE-2026-23877?

CVE-2026-23877 is a medium-severity path traversal vulnerability in swingmx swingmusic, published on 19 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Swing Music is a self-hosted music player for local audio files. Prior to version 2.1.4, Swing Music's `list_folders()` function in the `/folder/dir-browser` endpoint is vulnerable to directory traversal attacks. Any authenticated user (including non-admin) can browse arbitrary directories on the server filesystem. Version 2.1.4 fixes the issue.

Weakness: CWE-284 (Improper Access Control), CWE-25 (Path Traversal: '/../filedir')

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

3 open source packages ship an affected version, including swingmusic. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `swingmusic` | PyPI | All versions | 2.1.4 |
| `swingmusic` | PyPI | All versions | 2.1.4 |
| `swingmusic` | PyPI | All versions | 2.1.4 |

Products: Swingmx Swing Music.

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

Upgrade swingmusic to 2.1.4 or later.

## Is CVE-2026-23877 being exploited?

There is no known exploitation of CVE-2026-23877 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-23877 is a medium-severity path traversal vulnerability in swingmx swingmusic, published on 19 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23877 in the wild and no public exploit code.

Affected packages and fixed versions:
- swingmusic (PyPI): affected all versions; fixed in 2.1.4
- swingmusic (PyPI): affected all versions; fixed in 2.1.4
- swingmusic (PyPI): affected all versions; fixed in 2.1.4

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-23877/ (Markdown: https://insights.sbomify.com/CVE-2026-23877/index.md)
```

## Sources

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

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