<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-02T18:32:44.270020+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-118668</id>
    <title>fkie_cve-2026-118668</title>
    <updated>2026-11-02T18:32:44.297206+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>langgraph-api implements the LangGraph API for rapid development and testing. From 0.1.2 until 0.15.0, JavaScript or TypeScript custom authentication Store authorization handlers can return a rewritten namespace that is not carried across the runtime boundary and applied before the Store operation. An authenticated user can therefore access another user's Store namespace when a deployment relies on namespace rewriting for isolation, allowing unauthorized reads, overwrites, searches, or deletions. Python custom authentication and handlers that reject unauthorized namespaces instead of rewriting them are not affected. This issue is fixed in version 0.15.0.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-118668"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-4hm6-w6qq-w73v</id>
    <title>GHSA-4hm6-w6qq-w73v — LangGraph JavaScript custom authentication may permit cross-user Store access</title>
    <updated>2026-11-02T18:32:44.297303+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: langgraph-api</p>
<p>## Summary</p>
<p>LangGraph deployments using JavaScript or TypeScript custom authentication may fail to apply Store authorization changes returned by an authorization handler. In affected deployments, an authenticated user may be able to access Store data outside their authorized namespace.</p>
<p>## Required conditions</p>
<p>A deployment is affected only when all of the following conditions apply:</p>
<p>- It uses an affected `langgraph-api` version.
- It runs JavaScript or TypeScript custom authentication.
- Its Store authorization handler relies on rewriting the requested namespace to restrict each user to their own data.
- The attacker can authenticate as an ordinary user.
- Multiple users' data is stored through the affected authorization path.</p>
<p>Python custom authentication handlers are not affected. JavaScript or TypeScript handlers that reject unauthorized namespace requests instead of rewriting them are also not affected.</p>
<p>The attack does not require administrator privileges, user interaction, a race condition, or the bypass of another mitigation.</p>
<p>## Impact</p>
<p>An authenticated user may be able to read, overwrite, search, or delete Store data belonging to another user.</p>
<p>## Patches</p>
<p>The issue is fixed in `langgraph-api` version `0.15.0`. The server now carries changes made by a JavaScript or TypeScript authorization handler across the runtime boundary and applies them before performing the Store operation. It validates the resulting namespace after authorization and rejects the request if an…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-4hm6-w6qq-w73v"/>
  </entry>
</feed>
