The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Authorization Bypass Through User-Controlled Key vulnerabilities in an interactive lesson.
Start learningA fix was pushed into the master branch but not yet published.
langgraph is a Building stateful, multi-actor applications with LLMs
Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key due to a key collision in the default_cache_key() and _freeze() functions of langgraph/_internal/_cache.py, where _freeze() reduces a non-hashable object to (type_name, tobytes_output, shape) and drops distinguishing metadata such as numpy dtype and PIL image mode, size, and palette. An attacker can poison the result cache or obtain another user's cached result by submitting a numpy array or PIL image keyword argument that matches a victim's input byte-for-byte but differs in the dropped metadata, yielding an identical cache key. Exploitation requires the Functional API (@task or @entrypoint) called with keyword arguments, a CachePolicy using the default key function, a non-hashable argument exposing .tobytes(), and a shared or persistent cache in a multi-user deployment, while positional arguments are unaffected because a hashable tuple short-circuits the lossy branch.