What happened
VulnCheck published (2026-10-18) that LobsterAI encrypts exported provider API keys with a hardcoded 'lobsterai-APP' secret, letting anyone with the export file derive the key and decrypt every stored AI provider API key. CVSS 5.5 (v3.1) / 6.8 (v4.0), CWE-321.
Why it matters
A local-viewer entity who obtains an exported config can recover the raw API keys used to bill AI provider usage, enabling account takeover and cost abuse of the victim's LLM accounts.
Attack vector
Provider API keys are encrypted with the constant 'lobsterai-APP' password. An attacker with the providers export file derives the AES-GCM key via PBKDF2 using the embedded salt (CWE-321 hardcoded password) and recovers every stored third-party AI provider API key.
Affected systems
netease-youdao LobsterAI before 2026.10.16
Mitigation
Upgrade to LobsterAI 2026.10.16 (fix commit 1eb28c40d7e42d6cbade07874e6f6c068b6a9a64) and rotate any exported provider keys.