# CVE-2026-112014: LobsterAI before 2026.10.16 Hardcoded Password in Provider API Key Export

> Attackers can decrypt exported provider API keys using a hardcoded password, exposing sensitive third-party AI credentials.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-rpw3-ccp2-4v8w

## What is CVE-2026-112014?

CVE-2026-112014 is a medium-severity vulnerability in netease-youdao LobsterAI, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

LobsterAI before 2026.10.16 contains a hardcoded password vulnerability that allows attackers to decrypt exported provider API keys encrypted with the constant 'lobsterai-APP'. Attackers who obtain a providers export file can derive the AES-GCM key via PBKDF2 using the embedded salt and recover every third-party AI provider API key.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2026-112014 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112014 is a medium-severity vulnerability in netease-youdao LobsterAI, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-112014 in the wild and no public exploit code.

Affected product: netease-youdao LobsterAI. 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-112014/ (Markdown: https://insights.sbomify.com/CVE-2026-112014/index.md)
```

## Sources

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

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