Description
Letta through 0.16.8 contains an authentication bypass vulnerability that allows API callers to impersonate other users by supplying a self-asserted user_id HTTP header. Attackers can set user_id to another tenant's ID, even with LETTA_SERVER_SECURE enabled, to read and modify that user's agents, memory and configuration.
Published: 2026-10-20
Score: 8.6 High
EPSS: < 1% Very Low
KEV: No
Impact: Authentication bypass allowing cross‑tenant impersonation
Action: Immediate Patch
AI Analysis

Impact

Letta versions up to 0.16.8 contain an authentication bypass flaw that lets attackers set a self‑asserted user_id HTTP header to impersonate any tenant. Hijacking a tenant grants full read and write access to that tenant’s agents, memory, and configuration, effectively creating a complete compromise of the impersonated account. The weakness is classified as CWE‑639 – Insecure Direct Object Reference, reflecting the failure to enforce proper ownership checks on user‑supplied identifiers.

Affected Systems

The flaw exists in the open‑source LETTA project, specifically in the LeTTA package whose APIs are exposed by the server component. All deployments using LeTTA up to version 0.16.8 are affected; later releases contain a fix.

Risk and Exploitability

The CVSS score of 8.6 marks this a high severity vulnerability, and there is no EPSS data currently available. The vulnerability is not listed in the CISA KEV catalog, but its impact warrants immediate action. Attackers can exploit the flaw by sending crafted HTTP requests to any LeTTA server endpoint that accepts the user_id header, regardless of LETTA_SERVER_SECURE being enabled. The attack can be executed over the network by anyone who can reach the API without additional authentication controls.

Generated by OpenCVE AI on October 20, 2026 at 12:22 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade LeTTA to version 0.16.9 or later, where the user_id header is properly authenticated.
  • Restrict API access by implementing network segmentation or firewall rules so that only trusted hosts can reach the vulnerable endpoints.
  • Disable or scrub the user_id header in API requests if it is not essential for your deployment, ensuring that user identity is derived solely from authenticated sessions.

Generated by OpenCVE AI on October 20, 2026 at 12:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 21 Oct 2026 17:15:00 +0000

Type Values Removed Values Added
First Time appeared Letta-ai
Letta-ai letta
Vendors & Products Letta-ai
Letta-ai letta

Tue, 20 Oct 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 20 Oct 2026 01:15:00 +0000

Type Values Removed Values Added
Description Letta through 0.16.8 contains an authentication bypass vulnerability that allows API callers to impersonate other users by supplying a self-asserted user_id HTTP header. Attackers can set user_id to another tenant's ID, even with LETTA_SERVER_SECURE enabled, to read and modify that user's agents, memory and configuration.
Title Letta through 0.16.8 Cross-Tenant Impersonation via user_id Header
First Time appeared Letta
Letta letta
Weaknesses CWE-639
CPEs cpe:2.3:a:letta:letta:*:*:*:*:*:*:*:*
Vendors & Products Letta
Letta letta
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 8.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-10-20T13:48:37.840Z

Reserved: 2026-08-21T17:52:36.080Z

Link: CVE-2026-77937

cve-icon Vulnrichment

Updated: 2026-10-20T13:48:32.739Z

cve-icon NVD

Status : Deferred

Published: 2026-10-20T01:17:20.263

Modified: 2026-10-20T20:11:29.833

Link: CVE-2026-77937

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-21T16:46:46Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key