# CVE-2026-123208: noname v1.11.2 through v1.11.6.1 Missing Authentication in Electron Local File Server


- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-q48j-7m3q-9pj6

## What is CVE-2026-123208?

CVE-2026-123208 is a high-severity vulnerability in libnoname noname, published on 5 Nov 2026. 

### Official 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.

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

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


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

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

## Is CVE-2026-123208 being exploited?

There is no known exploitation of CVE-2026-123208 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123208 is a high-severity vulnerability in libnoname noname, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123208 in the wild and no public exploit code.

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

## Sources

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

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