Graylog server has partial path traversal vulnerability in Support Bundle featureGHSA-2q4p-f6gf-mqr5
LOWFix: Graylog2/graylog2-server@02b8792GHSA-2q4p-f6gf-mqr5 is a low-severity (CVSS 3.3) Path Traversal vulnerability in org.graylog2:graylog2-server. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.graylog2:graylog2-server — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2q4p-f6gf-mqr5.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.graylog2:graylog2-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A partial path traversal vulnerability exists in Graylog's Support Bundle feature. The vulnerability is caused by incorrect user input validation in an HTTP API resource.
Thanks to weiweiwei9811 for reporting this vulnerability and providing detailed information.
Impact
Graylog's Support Bundle feature allows an attacker with valid Admin role credentials to download or delete files in sibling directories of the support bundle directory.
The default data_dir in operating system packages (DEB, RPM) is set to /var/lib/graylog-server. The data directory for the Support Bundle feature is always <data_dir>/support-bundle.
Due to the partial path traversal vulnerability, an attacker with valid Admin role credentials can read or delete files in directories that start with a /var/lib/graylog-server/support-bundle directory name.
The vulnerability would allow the download or deletion of files in the following example directories.
/var/lib/graylog-server/support-bundle-test/var/lib/graylog-server/support-bundlesdirectory
For the Graylog and Graylog Enterprise Docker images, the data_dir is set to /usr/share/graylog/data by default.
Patches
The vulnerability is fixed in Graylog version 5.1.3 and later.
Workarounds
Block all HTTP requests to the following HTTP API endpoints by using a reverse proxy server in front of Graylog.
GET /api/system/debug/support/bundle/download/{filename}DELETE /api/system/debug/support/bundle/{filename}
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.graylog2:graylog2-server | ≥ 5.1.0&&< 5.1.3 | 5.1.3org.graylog2:graylog2-server:5.1.3 |
Affected Products
grayloggraylogResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.graylog2:graylog2-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.graylog2:graylog2-server to 5.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2q4p-f6gf-mqr5 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is GHSA-2q4p-f6gf-mqr5 in your dependencies?
Find it across Maven, including transitive dependencies.