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

LibreChat

LibreChat: agent edit authority must cover attached context

LibreChat could deny access to a private agent yet accept unauthorized additions to its context and search files. The maintainer advisory attributes this to upload handling that omitted the agent permission checks used elsewhere, and its demonstration changed the response visible to the owner. The failure was in application authorization before the model interpreted the added content.

Open the referenceMaintainer AdvisoryReviewed 2026-10-03

How to use this reference

The source recommends checking agent-edit permission for uploads. Editorial review principle: identify every way the information an agent uses can change, including attachments and retrieval indexes. Preventing users from viewing its configuration does not prevent unauthorized changes to that information.

Before reading

  • Object-level authorization and agent context composition

Context and limits

  • The advisory credits Lisa Gnedt and Michael Koppmann of SBA Research, with GitHub Reporter credits for lxp and mkoppmann. It does not display an explicit author byline; these credits alone do not establish advisory authorship, so named authors remain unestablished.
  • Requires an authenticated account and knowledge of another agent’s identifier; private agents were not ordinarily visible.
  • CVE-2025-69220: the advisory identifies 0.8.1-rc2 as affected and records the 0.8.2-rc2 fix release on January 7, 2026.
  • No production compromise, data theft, or award is established. Broader model behavior depends on application context; this review did not run the demonstration.

Sources

  1. LibreChat Insufficient Access Control on Agent FilesLibreChat · 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