/

CVE-2026-79665

Severity:

HIGH RISK

(8.8)

Authorization Bypass (CWE-862) in Ech0 Admin Endpoints

CVE-2026-79665

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-862

Impact:

Unauthorized administrative access and information disclosure

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Ech0 before 4.5.1 contains an authorization bypass in the RequireScopes middleware, where authenticated session tokens are accepted without validating the required access scope. A logged-in non-admin user may use this weakness to reach administrative endpoints and access sensitive operational and user data.

Affected context

The vulnerability occurs in Ech0 deployments where authenticated session tokens are processed by the RequireScopes middleware but their scopes are not properly checked before administrative endpoints are served. The affected attack surface may include endpoints exposing system logs, visitor statistics, user email addresses, and live WebSocket log streams.

Exploit preconditions

  • Attack surface: Authenticated HTTP and WebSocket endpoints protected by RequireScopes middleware
  • Required access: A valid logged-in session token, potentially belonging to a non-admin user
  • Trigger point: A request to an administrative or otherwise scope-restricted endpoint
  • Why exploitation is possible: The middleware accepts the session token without enforcing the scope required by the target endpoint

Why this happens

The underlying bug is an authorization enforcement failure mapped to CWE-862: Missing Authorization. The application authenticates the session token but does not reliably perform the separate authorization step that verifies whether the token's user has the required scope. This allows authentication status to be treated as sufficient for access to privileged functionality.

Potential impact

  • Non-admin users may access administrative endpoints
  • Attackers could read system logs and visitor statistics
  • User email addresses may be disclosed
  • Attackers may subscribe to live WebSocket log streams
  • Sensitive operational information could support further attacks
  • Application confidentiality and administrative control may be weakened

General mitigation guidance

Mitigation generally focuses on making authorization checks explicit, centralized, and fail-closed.

Common defensive patterns include:

  • Validate the required scope or permission for every protected endpoint
  • Treat authentication and authorization as separate enforcement decisions
  • Apply the same permission checks to HTTP and WebSocket routes
  • Deny access by default when scopes are missing, malformed, or ambiguous
  • Use narrowly scoped session tokens and minimize user privileges
  • Avoid relying on client-provided role or scope values without trusted server-side verification
  • Add regression tests covering non-admin access to every administrative route

How teams detect issues like this

Detection approaches commonly include:

  • Static analysis for middleware that authenticates tokens without checking endpoint permissions
  • Code review of route registration and authorization middleware composition
  • Tests that exercise privileged endpoints with valid tokens lacking the required scope
  • Integration tests covering both HTTP requests and WebSocket subscriptions
  • Runtime monitoring for non-admin identities accessing administrative routes or log streams
  • Policy enforcement requiring explicit authorization annotations or checks on sensitive endpoints
  • Automated security review tools that identify authentication-only protection on privileged resources

Sources

SourceLink
github.comgithub.com/lin-snow/Ech0/security/advisories/GHSA-hmmq-qh6g-6wgh
vulncheck.comvulncheck.com/advisories/ech0-before-authorization-bypass-via-session-tokens

Frequently asked

questions

The described issue requires a valid logged-in session token. An unauthenticated attacker would generally not meet this prerequisite, although the overall exposure depends on the application's authentication and session controls.

A non-admin user account may be sufficient because the flaw bypasses scope validation after authentication. The attacker does not necessarily need an administrative account.

Enforce server-side, endpoint-specific authorization checks for every administrative HTTP and WebSocket operation, using a default-deny behavior when the required scope is absent.

Separate authentication from authorization in design and testing, use centralized permission enforcement, apply least privilege to tokens, and include negative tests for lower-privileged users on all sensitive routes.

Find out what's already
exploitable in your codebase.