# CVE-2026-123206: EdgeChat before 2.20.3 Missing Authentication for Attachment Download via GET /files/:key


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-24j8-6f8g-7442

## What is CVE-2026-123206?

CVE-2026-123206 is a medium-severity vulnerability in aozorae EdgeChat, published on 5 Nov 2026. 

### Official description

EdgeChat before 2.20.3 contains a missing authentication vulnerability in the GET /files/:key route that allows unauthenticated or banned users to download decrypted public-channel attachments because canAccessFile() accepts a null user id. Attackers holding an attachment object key can omit or supply an invalid token to retrieve plaintext attachments without a session or channel membership.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-123206 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123206 is a medium-severity vulnerability in aozorae EdgeChat, published on 5 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123206 exists.

Affected product: aozorae EdgeChat. 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-123206/ (Markdown: https://insights.sbomify.com/CVE-2026-123206/index.md)
```

## Sources

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

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