Listing of upload directory contents possible
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/ThomasLeister/prosody-filer 1.0.1), 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
Go github.com/ThomasLeister/prosody-filer
- Affected
- < 1.0.1
- Fixed in
- 1.0.1
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-qmfx-75ff-8mw6 lists affected ranges: Go github.com/ThomasLeister/prosody-filer >=0 <1.0.1
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
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
There's an security issue in prosody-filer versions < 1.0.1 which leads to unwanted directory listings of download directories. An attacker is able to list previous uploads of a certain user by shortening the URL and accessing a URL subdirectors other than /upload/ (or the corresponding user defined root dir) Version 1.0.1 and later fix this problem and allow only direct file access if the full path is known. Directory listings are blocked entirely.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-qmfx-75ff-8mw6
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-qmfx-75ff-8mw6 Advisory: Listing of upload directory contents possible IDs: GHSA-qmfx-75ff-8mw6 Record: https://patchnext.com/advisories/ghsa-qmfx-75ff-8mw6 (revision 1, source checked 26 Oct 2026, 14:54 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/ThomasLeister/prosody-filer 1.0.1. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/ThomasLeister/prosody-filer: affected < 1.0.1; fixed in 1.0.1 ## Suggested inspection (read-only) - Go github.com/ThomasLeister/prosody-filer: check the installed version with your package manager. ## 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 github.com/ThomasLeister/prosody-filer. - 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://github.com/advisories/GHSA-qmfx-75ff-8mw6 (GitHub-reviewed advisory GHSA-qmfx-75ff-8mw6 lists affected ranges: Go github.com/ThomasLeister/prosody-filer >=0 <1.0.1) Commands are suggestions: review each one before running it.
Loading voting…