LobsterAI fixes provider exports that exposed saved API keys

LobsterAI's default Export Providers flow encrypted configured provider API keys with a fixed password present in the open-source code. The export included a random salt, but the password was shared across installations and could be recovered from the public source. Anyone who obtained a file created by that default flow could derive its encryption key and recover the provider keys it contained. The issue therefore depended on access to an exported file, such as a copy placed in shared storage or an email attachment. Public sources reviewed here describe the exposure condition and code fix; they do not document a confirmed victim count or real-world API abuse. (LobsterAI issue #2851; GitHub advisory CVE-2026-112014)

What changed

LobsterAI merged PR #2863 on October 14. The updated default export contains provider configuration without API keys. A separate authenticated backup flow can include credentials using a user-supplied password. The change also preserves imports from earlier export formats. The project's 2026.10.16 release lists secure provider exports and legacy-import support among its fixes. The updated export implementation shows the default path omitting API keys and the authenticated path encrypting credentials.

The GitHub advisory calls out versions before 2026.10.16, while its affected and patched version fields remain unknown. The public record does not define a more precise affected range. Confirm the version and export behavior in the exact build you distribute.

What teams should review

• Upgrade to a build containing the 2026.10.16 export fix, and verify that its default provider export omits credentials.
• Locate older provider exports in backup folders, synchronized drives, support tickets, and email attachments. Restrict access to retained copies and remove them when they are no longer needed.
• If an older credential-bearing export may have left controlled storage, rotate the included provider keys and review provider usage. This is Kalyxo's practical guidance based on the exposed credential type; it is not a claim that any key was accessed or misused.
• Treat password-protected credential backups as sensitive files. Use a unique password and store it separately from the backup.

A software update changes how new exports are made; it cannot recall files already copied elsewhere. The sources reviewed for this report document a repository issue, its fix, and an advisory. They do not establish exploitation in the wild or a customer breach.