Description

A vulnerability was found in getzep graphiti up to 0.30.2. Affected is an unknown function of the file server/graph_service/main.py of the component REST API. The manipulation results in improper authentication. The attack can be launched remotely. The pull request to fix this issue awaits acceptance.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.3",
  "pubDate": "2026-09-13T23:16:28.343Z",
  "pubdate": "2026-09-13T23:16:28.343Z",
  "executiveSummary": "A critical vulnerability has been identified in the getzep graphiti component, specifically within the REST API implementation found in server/graph_service/main.py. The vulnerability is classified as an improper authentication flaw, allowing remote, unauthenticated actors to bypass established security controls.\nThe flaw affects all versions of graphiti up to and including 0.30.2. The security risk is significant as it potentially grants unauthorized access to sensitive graph data or administrative functions handled by the affected API endpoint.\nBecause the attack vector is remote, it does not require physical access to the server infrastructure, lowering the barrier to entry for potential adversaries. Successful exploitation undermines the integrity and confidentiality of the application, as the system fails to correctly verify the identity of the requester before processing sensitive requests. Organizations currently running versions 0.30.2 or earlier are at risk until the pending security patch is applied.",
  "technicalDetails": "The vulnerability resides within the REST API architecture of the graphiti server, specifically originating from logic errors located in server/graph_service/main.py. The root cause pertains to a failure in the authentication middleware or the validation logic responsible for verifying request credentials prior to executing service operations.\nThe attack flow initiates with a remote adversary crafting a specifically formatted HTTP request targeted at the affected REST API endpoint. Due to the lack of rigorous authentication enforcement in the service layer, the application fails to validate the authorization tokens or session integrity associated with the incoming request. Consequently, the server proceeds to execute the requested graph operations as if the user were authenticated.\nThe vulnerable component, server/graph_service/main.py, lacks the necessary checks to reject unauthorized requests, effectively granting the requester the ability to interact with internal graph services. Because this is an authentication bypass, the attacker does not need to provide valid credentials. The scope of impact is highly dependent on the functionality exposed by the affected function; however, in the context of a graph service API, this typically includes unauthorized data retrieval, manipulation of graph structures, or potential exfiltration of proprietary information stored within the graph database.\nThe vulnerability is persistent across all versions up to 0.30.2, indicating a systemic flaw in the authentication handling mechanism rather than an isolated regression. There are no specialized privilege requirements for an attacker to initiate this request, as the flaw bypasses the verification stage entirely. The network exposure is high, given that the REST API is designed for remote service communication, making any publicly or internally exposed instance a target for exploitation.\nPost-exploitation, an adversary could achieve unauthorized read or write access to the graph store, leading to data corruption, information leakage, or further exploitation of downstream systems that trust the integrity of the graphiti API output. The current lack of a finalized patch necessitates that administrators monitor incoming traffic for anomalous request patterns targeting the graph service."
}