EdgeChat before 2.20.3 Missing Authentication for Attachment Download via GET /files/:key
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 2.20.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.20.3.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 38/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
EdgeChat versions before 2.20.3 have a missing authentication flaw in the file download route that lets someone remotely, without logging in, download decrypted attachments from public channels. An attacker needs to hold the attachment's object key, and the bug also lets unauthenticated or banned users retrieve these files without a session or channel membership.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 43 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.20.3.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- aozorae EdgeChat
fixed in 2.20.3
Evidence 5
- Patch
- Report
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123206
Is CVE-2026-123206 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-123206?
EdgeChat: before 2.20.3.Source: cve.now feed data
How do I fix CVE-2026-123206?
Upgrade to a fixed version: 2.20.3.Source: cve.now feed data