Ech0's Missing Authorization on System Logs Allows Non-Admin Information Disclosure

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary The system log endpoints (GET /api/system/logs, GET /api/system/logs/stream, WS /ws/system/logs) lack authorization checks, allowing any authenticated non-admin user to read and stream all server logs. These logs contain error stack traces, internal file paths, module names, and arbitrary structured fields that facilitate reconnaissance for further attacks. Details The dashboard routes in internal/router/dashboard.go:7-8 register log endpoints on the AuthRouterGroup without any RequireScopes middleware: Compare with other admin-only routes that properly use RequireScopes: The AuthRouterGroup only applies JWTAuthMiddleware() (router.go:36), which validates the JWT and sets the viewer context but does not check admin status. The WSRouterGroup (router.go:37) has no middleware at all — the WebSocket handler only calls ParseToken to verify the JWT signature (dashboard.go:74) without any role/scope validation. The handler (internal/handler/dashboard/dashboard.go:29-62) and service…

Published by the source

10 Apr 2026, 19:49 UTC

Last modified by the source

10 Apr 2026, 19:49 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w8jj-cwmc-wgq2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-w8jj-cwmc-wgq2

Advisory: Ech0's Missing Authorization on System Logs Allows Non-Admin Information Disclosure
IDs: GHSA-w8jj-cwmc-wgq2
Record: https://patchnext.com/advisories/ghsa-w8jj-cwmc-wgq2 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/lin-snow/ech0 4.4.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/lin-snow/ech0: affected < 4.4.3; fixed in 4.4.3

## Suggested inspection (read-only)
- Go github.com/lin-snow/ech0: 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/lin-snow/ech0.
- 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-w8jj-cwmc-wgq2 (GitHub-reviewed advisory GHSA-w8jj-cwmc-wgq2 lists affected ranges: Go github.com/lin-snow/ech0 >=0 <4.4.3)

Commands are suggestions: review each one before running it.