Threat Intelligence Database

Mem0 versions through 0.2.8, fixed in commit ae7f406, contain a missing authorization vulnerability in the self-hosted server component where the POST /configure endpoint modifies global LLM provider and embedder configuration but only verifies authentication via JWT or X-API-Key without validating the caller's role. Any authenticated user holding a distributed API key can redirect all LLM and embedder traffic to an attacker-controlled server, with the malicious configuration persisted to PostgreSQL and surviving server restarts to affect all users and API keys on the instance.

The mem0 1.0.0 server has a vulnerability in its memory creation API endpoint (POST /memories) due to lack of authentication and authorization controls. This allows unauthenticated remote attackers to submit arbitrary memory records without identity or permission verification, potentially injecting unauthorized or malicious data into the database. The vulnerability is rated medium severity with a CVSS score of 5.3. No official patch or remediation guidance is currently available, and no known exploits have been reported in the wild.

The mem0 1.0.0 server has a vulnerability where its DELETE /memories endpoint lacks authentication and authorization controls. This allows an unauthenticated attacker to trigger a memory reset operation that executes a CREATE TABLE SQL statement. The consequence can be unexpected table re-creation, disruption of the database schema, potential data loss, and denial of service for the memory management service. The vulnerability has a medium severity with a CVSS score of 6.5. No patch or official remediation guidance is currently available.

The mem0 v1.0.0 server lacks authentication and authorization controls for its memory reset functionality accessible via the DELETE /memories endpoint. An unauthenticated attacker can send a DELETE request that triggers a reset operation, leading to the execution of a DROP TABLE SQL statement. This results in the deletion of the entire memory database table, causing catastrophic data loss and a complete denial of service for all users of the service.

The mem0 1.0.0 server lacks authentication and authorization controls for its memory management API endpoints. Critical functions such as updating memory records (PUT /memories/{memory_id}) are exposed without any verification of the requester's identity or permissions. A remote attacker can exploit this by sending unauthenticated requests to modify, overwrite, or delete arbitrary memory records, leading to unauthorized data manipulation and potential data loss.

A vulnerability was found in mem0ai mem0 up to 1.0.11. This affects the function pickle.load/pickle.dump of the file mem0/vector_stores/faiss.py. Performing a manipulation results in deserialization. It is possible to initiate the attack remotely. The exploit has been made public and could be used. The patch is named 62dca096f9236010ca15fea9ba369ba740b86b7a. Applying a patch is the recommended action to fix this issue.