LobsterAI before 2026.10.16 Hardcoded Password in Provider API Key Export
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| netease-youdao | LobsterAI | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Netease-youdao | Lobsterai |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.126% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Netease-youdao
Netease-youdao lobsterai |
|
| Vendors & Products |
Netease-youdao
Netease-youdao lobsterai |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | LobsterAI before 2026.10.16 Hardcoded Password in Provider API Key Export | |
| Weaknesses | CWE-321 | |
| References |
|
|
| Metrics |
cvssV3_1
|