CVE-2026-90601

getzep · graphiti

An improper authentication vulnerability in the getzep graphiti REST API allows remote attackers to bypass security controls via the server/graph_service/main.py component.

Executive summary

A remote, unauthenticated authentication bypass vulnerability exists in getzep graphiti versions up to 0.30.2, posing a significant risk to API security and data integrity.

Vulnerability

The application suffers from improper authentication (CWE-287) within the REST API component located at server/graph_service/main.py. This flaw permits unauthenticated remote attackers to interact with the service without valid credentials.

Business impact

This vulnerability carries a CVSS score of 7.3, reflecting its high severity due to the lack of required authentication and ease of remote exploitation. Successful exploitation could lead to unauthorized access to sensitive graph data or system functionality, potentially resulting in data exfiltration or unauthorized manipulation of the service.

Remediation

Immediate Action: Monitor the official getzep graphiti GitHub repository for the merge and release of the fix provided in pull request 1739. Once the patch is released, update the software to the corrected version immediately.

Proactive Monitoring: Review API access logs for anomalous, unauthenticated requests originating from unknown or suspicious IP addresses. Monitor system health for unexpected behavior within the graph_service module.

Compensating Controls: Deploy a Web Application Firewall (WAF) with custom rules designed to intercept or block unauthorized access attempts targeting the graph_service/main.py endpoint. Restrict network access to the API to trusted internal IP ranges until a permanent patch is applied.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

Given the high CVSS score and the critical nature of an authentication bypass, organizations currently utilizing getzep graphiti should treat this as a priority. Administrators must track the development of the pending security update and apply it as soon as it becomes available to prevent unauthorized access to the underlying data environment.

History

  1. Collected by CVE Brief via github
  2. Held for re-check analysis graded thin
  3. Analyst report written

Sources

Originally found and disclosed by Default01 (VulDB User), with VulDB CNA Team (coordinator), per the CVE Program record.