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

Published Oct 18, 2026
·
Updated

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.

Affected Software

1 affected component
LobsterAI LobsterAI<2026.10.16

Event History

Oct 18, 2026
CVE Published
via MITRE·11:38 AM
Data Sourced
via MITRE·11:38 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What must an attacker obtain to recover the provider API keys?

An attacker needs a providers export file. With that file, the hardcoded password, and the embedded salt, they can derive the AES-GCM key using PBKDF2 and decrypt every exported third-party AI provider API key.

2

Which deployments are affected?

LobsterAI versions before 2026.10.16 are affected. The issue concerns provider API keys included in exported providers files.

3

What is the practical impact if an export file is exposed?

Exposure can reveal every third-party AI provider API key stored in the export. Those keys should be treated as compromised and rotated with their respective providers.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203