noname v1.11.2 through v1.11.6.1 Missing Authentication in Electron Local File Server
Affects the Electron desktop build of noname v1.11.2 through v1.11.6.1, whose local file server on port 8089 starts automatically with the app and has no authentication.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Electron desktop build of noname The app is running; the local server starts automatically at startup A page is open in a browser on the same machine while the app is running
- 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? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- 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
Summary
The noname Electron desktop build from v1.11.2 through v1.11.6.1 runs an unauthenticated local file server with wildcard CORS, so a malicious website can read, overwrite, or delete installation files. An attacker can reach it remotely without logging in, but the victim must visit the malicious site, and overwriting renderer scripts can lead to JavaScript running with Node.js access as the local user.
Read the original description
noname Electron desktop build v1.11.2 through v1.11.6.1 contains an unauthenticated local file server with wildcard CORS that allows malicious websites to read, overwrite, or delete installation files. Attackers can send cross-origin requests to /writeFile on localhost port 8089 to overwrite renderer scripts, executing JavaScript with Node.js access as the local user.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.7/10CVSS 7.7
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Electron desktop build of noname The app is running; the local server starts automatically at startup A page is open in a browser on the same machine while the app is runningApply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- libnoname noname
From v1.11.2 · through v1.11.6.1
Evidence 6
- Patch
- Patch
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123208
Is CVE-2026-123208 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. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The local file server on port 8089 does not require authentication. A web page open in a browser on the same machine while the app is running can read, write, or delete files in the app's installation directory. Overwriting the renderer bundle leads to Node.js code execution on the next window load.Source: github.com
Which versions are affected by CVE-2026-123208?
noname: from v1.11.2 through v1.11.6.1.Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are v1.11.2 through v1.11.6.1 of noname, in the Electron desktop build, which bundles @noname/fs. The local server starts automatically at application startup, so check the installed version and whether the Electron desktop build is in use.Source: github.com
How do I fix CVE-2026-123208?
The checked facts do not name a fixed version or a workaround. Check the vendor's advisory for an update that addresses this issue.Source: github.com
Why do the sources disagree?
The description describes a local attack, while the CVSS vector records a network attack vector (AV:N). Both descriptions are shown in the source data without a resolution.Source: github.com