EUVD-2026-53700
GHSA-c8v3-2w4m-9q57
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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
Unauthenticated network-accessible endpoint with no complexity or prerequisites; scope unchanged with low confidentiality, integrity, and availability impact consistent with status-route metadata exposure.
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
Lifecycle Timeline
1DescriptionCVE.org
A vulnerability was detected in letta-ai LettaBot 0.2.0. Impacted is an unknown function of the file src/api/server.ts of the component API Status Route. The manipulation results in missing authentication. The attack may be performed from remote. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
AnalysisAI
Authentication bypass in letta-ai LettaBot 0.2.0 exposes the API Status Route in src/api/server.ts to unauthenticated remote access, allowing any network-reachable attacker to interact with the endpoint without credentials. The root cause is missing authentication enforcement (CWE-287) on what should be a protected API handler, with confidentiality, integrity, and availability each assessed at low impact per the CVSS 4.0 vector. A public proof-of-concept exploit exists (GitHub Gist, corroborated by CVSS 4.0 E:P), and the vendor did not respond to responsible disclosure, leaving no patch available at time of analysis.
Technical ContextAI
LettaBot 0.2.0 is an AI agent framework component by letta-ai, implemented with a TypeScript server file (src/api/server.ts), consistent with a Node.js/Express.js-style backend. The API Status Route is a specific endpoint handler within that server that fails to enforce any authentication check before processing incoming requests - the root cause class is CWE-287 (Improper Authentication). In Node.js REST API frameworks, this commonly manifests as a route registered without authentication middleware, or where middleware is applied globally but explicitly bypassed for a particular route. Status routes in such frameworks typically surface service health, version metadata, or runtime configuration data, making them attractive for reconnaissance even when direct code execution is not possible.
RemediationAI
No vendor-released patch has been identified at time of analysis; the vendor did not respond to responsible disclosure, so no official fix version exists. As the most effective compensating control, operators should restrict network access to the LettaBot API port using firewall rules or reverse proxy access controls, limiting reachability to trusted internal IP ranges only - this directly counters the AV:N attack vector with minimal functional impact, since status routes are typically consumed by internal monitoring systems. Alternatively, adding authentication middleware to the specific route handler in src/api/server.ts (e.g., requiring a valid API key or bearer token) addresses the root cause directly within the codebase, though this requires local modification and testing. Disabling or removing the API Status Route entirely is the most conservative option if the endpoint is not operationally required. Organizations should monitor the letta-ai upstream repository for any patch releases. POC reference: https://gist.github.com/YLChen-007/2ba2e586f3d16cb368c8dcd6ef680178. VulDB entry: https://vuldb.com/vuln/386359
Same weakness CWE-287 – Improper Authentication
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today