vulns.co
/
GKData.io MCP and API Buy me a coffee

LibreChat

LibreChat: viewing an integration must not reveal its service secrets

LibreChat returned decrypted integration configuration to viewers without removing service secrets. Its maintainer advisory describes a local demonstration in which a view-only account received administrator-managed provider credentials. Configuration prepared for internal use was therefore unsafe to reuse as a viewer response.

Open the referenceMaintainer AdvisoryReviewed 2026-10-03

How to use this reference

The source recommends removing secrets from responses and, where useful, indicating only whether a secret is configured. Editorial review principle: keep configuration used to run an integration separate from data shown to viewers. Check that both list and detail responses enforce the same rules about which fields a viewer may see.

Before reading

  • Integration credentials, response serialization, and object versus field authorization

Context and limits

  • Requires MCP enabled, stored administrator-managed secrets, and viewer access to the shared integration.
  • CVE-2026-44653: affected v0.8.3 and patched v0.8.4 are listed; patch release date is not established by the advisory. March 13 is the reported test date, not publication.
  • Credential reuse and indirect exposure through shared agents are possible extensions discussed by the source, not demonstrated outcomes. No production compromise or award is established.

Sources

  1. Shared MCP Server View Leaks Decrypted Admin SecretsLibreChat · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software