Swing Music has a Directory Traversal & Filesystem can be accessed by a non-admin user
CVE-2026-23877GHSA-pj88-9xww-gxmh
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (swingmusic 2.1.4), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI swingmusic
- Affected
- < 2.1.4
- Fixed in
- 2.1.4
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-pj88-9xww-gxmh lists affected ranges: PyPI swingmusic >=0 <2.1.4 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-pj88-9xww-gxmh lists affected ranges: PyPI swingmusic >=0 <2.1.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 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 · score source
- EPSS
- CVE-2026-23877: 0.60% estimated exploitation activity in the next 30 days; percentile 48.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Swing Music's listfolders() 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. Details The @api.post("/dir-browser") endpoint lacks proper path validation and authorization checks: - No authorization requirement: Any authenticated user can access the endpoint - Improper path handling: The code attempts to prepend "/" to non-existent paths but this doesn't prevent traversal: PoC 1. Create a non-admin user 2. Authenticate as a non-admin user 3. Send the following request: 4. The response will list directories from /proc/self instead of restricting to user-accessible paths: Impact Information Disclosure: - Server filesystem structure and layout - Configuration file locations and names - User account names from directory listings - Software versions and installed packages - Log file locations and system paths Additional Risks: -…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-pj88-9xww-gxmh
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-pj88-9xww-gxmh
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-23877 Advisory: Swing Music has a Directory Traversal & Filesystem can be accessed by a non-admin user IDs: CVE-2026-23877, GHSA-pj88-9xww-gxmh Record: https://patchnext.com/advisories/cve-2026-23877 (revision 3, source checked 26 Oct 2026, 13:36 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: swingmusic 2.1.4. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI swingmusic: affected < 2.1.4; fixed in 2.1.4 ## Suggested inspection (read-only) - `python -m pip show swingmusic`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on swingmusic. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-pj88-9xww-gxmh (OSV record GHSA-pj88-9xww-gxmh lists affected ranges: PyPI swingmusic >=0 <2.1.4 (fixed)) - Verified: https://github.com/advisories/GHSA-pj88-9xww-gxmh (GitHub-reviewed advisory GHSA-pj88-9xww-gxmh lists affected ranges: PyPI swingmusic >=0 <2.1.4) Commands are suggestions: review each one before running it.
Loading voting…