{"id":"CVE-2026-112014","kind":"vulnerability","aliases":["CVE-2026-112014"],"related":[],"title":"LobsterAI: hardcoded password lets attackers decrypt exported AI provider API keys","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.","summary":"LobsterAI before 2026.10.16 encrypts exported provider API keys with a constant password, 'lobsterai-APP', that is embedded in the software. An attacker who obtains an exported providers file can derive the decryption key and recover every stored third-party AI provider API key.","severity":"medium","cvss":6.8,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["ai-api-keys","ai-tooling","desktop-app","lobsterai"],"not_affected_if":["never-exports-providers","version-2026.10.16-or-later"],"how_to_check":"- Check the installed LobsterAI version and whether it is earlier than `2026.10.16`\n- Look for any exported providers file that was created by LobsterAI before the upgrade\n- unknown whether the sources give a command to confirm the installed version","fix":"- Upgrade LobsterAI to `2026.10.16` or later\n- Rotate every third-party AI provider API key that was stored in LobsterAI or included in an exported providers file\n- Delete old providers export files that were created before the upgrade","status":"open","published_at":"2026-10-18T12:17:14+00:00","first_seen_at":"2026-10-23T21:57:15+00:00","triaged_at":"2026-10-25T03:45:03+00:00","updated_at":"2026-10-25T03:45:03+00:00","category":"ai-tooling","confidence":0.7,"triage":{"at":"2026-10-25T03:45:03Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade LobsterAI to `2026.10.16` or later\n- Rotate every third-party AI provider API key that was stored in LobsterAI or included in an exported providers file\n- Delete old providers export files that were created before the upgrade","reach":"local","title":"LobsterAI: hardcoded password lets attackers decrypt exported AI provider API keys","impact":"medium","summary":"LobsterAI before 2026.10.16 encrypts exported provider API keys with a constant password, 'lobsterai-APP', that is embedded in the software. An attacker who obtains an exported providers file can derive the decryption key and recover every stored third-party AI provider API key.","category":"ai-tooling","nicknames":[],"who_cares":["lobsterai","ai-api-keys","desktop-app"],"confidence":0.7,"needs_auth":"unknown","worst_case":"Attacker recovers all stored third-party AI provider API keys from an export file","analyst_note":"Check the NVD entry or vendor advisory for how the export file is created and whether a default install exports providers automatically; confirm the exact fixed version and any command to check it.","how_to_check":"- Check the installed LobsterAI version and whether it is earlier than `2026.10.16`\n- Look for any exported providers file that was created by LobsterAI before the upgrade\n- unknown whether the sources give a command to confirm the installed version","needs_analyst":true,"not_affected_if":["version-2026.10.16-or-later","never-exports-providers"],"who_is_affected":"Teams that use LobsterAI before version 2026.10.16 and export provider settings, since the export file holds the provider API keys encrypted with a password that is hardcoded in the product. Anyone who can read such an export file can recover the keys, so the risk depends on where those files are stored and shared. Teams on 2026.10.16 or later, or that never export providers, can skip the key rotation step.","user_interaction":"yes","needs_special_setup":"unknown","severity_if_unknown":"medium"},"cost_usd":0.000679,"input_tokens":3343,"output_tokens":689,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-112014':14A,17A '-2026':13A,16A '2026.10.16':31B,76C 'ae':109C 'aes-gcm':108C 'ai':8A,19B,23B,70B,124C 'ai-api-key':18B 'ai-tool':22B 'allow':83C 'api':10A,20B,35B,72B,89C,126C 'app':27B,43B,97C 'attack':5A,51B,84C,98C 'constant':39B,94C 'contain':77C 'cve':12A,15A 'decrypt':6A,61B,86C 'deriv':59B,106C 'desktop':26B 'desktop-app':25B 'embed':46B,116C 'encrypt':32B,91C 'everi':65B,120C 'export':7A,33B,55B,87C,103C 'file':57B,104C 'gcm':110C 'hardcod':2A,79C 'key':11A,21B,36B,62B,73B,90C,111C,127C 'let':4A 'lobsterai':1A,28B,29B,42B,74C,96C 'lobsterai-app':41B,95C 'obtain':53B,100C 'parti':69B,123C 'password':3A,40B,80C 'pbkdf2':113C 'provid':9A,34B,56B,71B,88C,102C,125C 'recov':64B,119C 'salt':117C 'softwar':49B 'store':66B 'third':68B,122C 'third-parti':67B,121C 'tool':24B 'use':114C 'via':112C 'vulner':81C","nicknames":[],"mitigations":[],"who_affected":"Teams that use LobsterAI before version 2026.10.16 and export provider settings, since the export file holds the provider API keys encrypted with a password that is hardcoded in the product. Anyone who can read such an export file can recover the keys, so the risk depends on where those files are stored and shared. Teams on 2026.10.16 or later, or that never export providers, can skip the key rotation step.","tier":"B","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-18T12:17:14+00:00","kev":null,"cvss_vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cvss_by":"disclosure@vulncheck.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-112014","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-112014","severity":null,"published_at":"2026-10-18T12:17:14+00:00","modified_at":"2026-10-20T16:17:01+00:00","first_seen_at":"2026-10-23T21:57:15+00:00","fetched_at":"2026-10-23T22:28:55+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}