# CVE-2026-79665: Ech0 before 4.5.1 Authorization Bypass via Session Tokens

> Logged-in non-admin users can bypass scope validation to access admin endpoints, reading system logs and user data.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-hmmq-qh6g-6wgh, GHSA-q8hh-m6v5-4f3x

## What is CVE-2026-79665?

CVE-2026-79665 is a high-severity missing authorization vulnerability in lin-snow Ech0, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ech0 before 4.5.1 contains an authorization bypass vulnerability where session tokens skip scope validation in RequireScopes middleware, allowing logged-in non-admin users to access admin endpoints. Attackers can read system logs, visitor statistics, user emails, and subscribe to live WebSocket logs by sending authenticated session tokens to unprotected endpoints.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-79665?


## How do I fix CVE-2026-79665?

No fix has been published for CVE-2026-79665 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-79665 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79665 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-79665 and fix it if it is affected.

What it is: CVE-2026-79665 is a high-severity missing authorization vulnerability in lin-snow Ech0, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-79665 exists.

Affected product: lin-snow Ech0. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-79665/ (Markdown: https://insights.sbomify.com/CVE-2026-79665/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-79665
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-79665
- OSV: https://osv.dev/vulnerability/CVE-2026-79665

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-79665/
Summaries are generated and may contain mistakes; the official description above is the record.