CVE-2026-27734
Received Received - Intake
Path Traversal in Beszel API Allows Docker Endpoint Exposure

Publication date: 2026-02-27

Last updated on: 2026-03-04

Assigner: GitHub, Inc.

Description
Beszel is a server monitoring platform. Prior to version 0.18.2, the hub's authenticated API endpoints GET /api/beszel/containers/logs and GET /api/beszel/containers/info pass the user-supplied "container" query parameter to the agent without validation. The agent constructs Docker Engine API URLs using fmt.Sprintf with the raw value instead of url.PathEscape(). Since Go's http.Client does not sanitize `../` sequences from URL paths sent over unix sockets, an authenticated user (including readonly role) can traverse to arbitrary Docker API endpoints on agent hosts, exposing sensitive infrastructure details. Version 0.18.4 fixes the issue.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-27
Last Modified
2026-03-04
Generated
2026-05-07
AI Q&A
2026-02-27
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
beszel beszel to 0.18.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :

An attacker who is authenticated, including those with readonly roles, can exploit this vulnerability to traverse to arbitrary Docker API endpoints on the agent hosts. This unauthorized access can expose sensitive infrastructure details, potentially revealing critical information about the monitored environment. Such exposure can lead to further attacks or compromise of the infrastructure.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, upgrade Beszel to version 0.18.4 or later, where the issue has been fixed.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


Can you explain this vulnerability to me?

This vulnerability exists in the Beszel server monitoring platform prior to version 0.18.2. The issue is that the authenticated API endpoints GET /api/beszel/containers/logs and GET /api/beszel/containers/info accept a user-supplied "container" query parameter without validating it. The agent then uses this raw value to construct Docker Engine API URLs without proper escaping. Because Go's http.Client does not sanitize "../" sequences in URL paths sent over unix sockets, an authenticated user, even with readonly role, can perform directory traversal to access arbitrary Docker API endpoints on the agent hosts. This can expose sensitive infrastructure details. The issue was fixed in version 0.18.4.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart