← All advisories
CVE-2026-54044highSecret exposure2026-11-20

CVE-2026-54044: In LibreChat, a collaborator with EDIT access to a shared agent could repoint an action to their own server and receive the owner's stored API key (fixed 0.8.7)

LibreChat agents can carry Actions: OpenAPI-described tools whose API key (or OAuth client secret) the agent owner stores encrypted and LibreChat sends as a Bearer token whenever the model calls the tool. Before 0.8.7, POST /api/agents/actions/:agent_id merged an editor's new metadata.domain and metadata.raw_spec into the existing action but kept the owner's api_key and OAuth client secrets. A collaborator the owner had shared the agent with at EDIT permission could swap the spec and domain to a host they control, and the next time the agent ran the tool LibreChat decrypted the owner's credential and sent it there. Fixed in 0.8.7.

01.

What it is

The vulnerable route is POST /api/agents/actions/:agent_id in api/server/routes/agents/actions.js. It loads the existing action with the owner's credentials and merges in editor-controlled metadata.domain and metadata.raw_spec while preserving metadata.api_key and related OAuth client secrets.

The attacker needs EDIT permission on a shared agent. One request is enough; the credential leaks on the next tool invocation by anyone using the agent.

The fix (commit 07af6ee, PR #13559) drops preserved secrets when the action's destination or auth settings change.

Affected: LibreChat before 0.8.7. v0.8.7 was released on 24 June 2026; GitHub published the advisory on 17 November 2026 and NVD the CVE on 20 November 2026.

02.

How to check

  1. Check your LibreChat version (release tag or container image tag).
  2. List agents that have Actions with stored API keys or OAuth secrets and are shared with other users at EDIT permission.
  3. Review action domains for hosts you don't recognise.
03.

How to fix

  1. Upgrade LibreChat to 0.8.7 or later (the current release also includes the later fixes).
  2. If shared agents with stored action keys had EDIT collaborators on an older version, rotate those API keys and OAuth client secrets.
  3. Share agents with credentials at view/use permission only unless editors are fully trusted.
# which LibreChat image/version is running?
docker ps --format '{{.Image}}' | grep -i librechat
04.

Sources

More advisories for this tool
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.