Ech0: Missing authorization on dashboard log endpoints allows low-privilege users to access sensitive system logs

Exploitation

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

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Ech0 allows any authenticated user to read historical system logs and subscribe to live log streams because the dashboard log endpoints validate only that a JWT is present and valid, but do not require an administrator role or privileged scope. Impact Any valid user session can access GET /api/system/logs and can also connect to the SSE and WebSocket log streaming endpoints. This exposes operational log data to low-privilege users. Depending on deployment and logging practices, the returned logs may include internal file paths, stack traces, admin activity, background job output, internal URLs, and other sensitive operational context. This creates a post-authentication information disclosure primitive that can materially aid follow-on attacks. Details The issue is caused by an authorization gap between route registration, handler logic, and the service layer. internal/router/dashboard.go registers the log endpoints on authenticated router groups, but does not apply any…

Published by the source

10 Apr 2026, 19:40 UTC

Last modified by the source

2 Jun 2026, 11:30 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cp79-9mwr-wr49

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

# Patch Next advisory brief: GHSA-cp79-9mwr-wr49

Advisory: Ech0: Missing authorization on dashboard log endpoints allows low-privilege users to access sensitive system logs
IDs: GHSA-cp79-9mwr-wr49
Record: https://patchnext.com/advisories/ghsa-cp79-9mwr-wr49 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
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.3.5. A vendor fix does not mean a deployment is fixed.

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

## 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-cp79-9mwr-wr49 (GitHub-reviewed advisory GHSA-cp79-9mwr-wr49 lists affected ranges: Go github.com/lin-snow/ech0 >=0 <4.3.5)

Commands are suggestions: review each one before running it.