<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 06:22:19 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-104873</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-104873</link>
      <description>&lt;p&gt;LangGraph Python SDK is used to connect to running LangGraph API servers, manage assistants, threads and stream runs from Python applications. From 0.1.45 until 0.4.4, the langgraph-sdk resource-scoped authorization decorators @auth.on.threads, @auth.on.assistants, and @auth.on.crons ignore the actions argument and register the selected handler for every action on the resource. Because that wildcard resource handler is selected before broader fallback handlers, an authenticated user may bypass fallback action, ownership, or permission checks and read, update, or delete another user&amp;#39;s resource. Only Python deployments using actions on the affected decorators are vulnerable, and a deployment remains protected when the selected handler independently enforces all required checks for every action it receives. This issue is fixed in version 0.4.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;LangGraph Python SDK is used to connect to running LangGraph API servers, manage assistants, threads and stream runs from Python applications. From 0.1.45 until 0.4.4, the langgraph-sdk resource-scoped authorization decorators @auth.on.threads, @auth.on.assistants, and @auth.on.crons ignore the actions argument and register the selected handler for every action on the resource. Because that wildcard resource handler is selected before broader fallback handlers, an authenticated user may bypass fallback action, ownership, or permission checks and read, update, or delete another user&amp;#39;s resource. Only Python deployments using actions on the affected decorators are vulnerable, and a deployment remains protected when the selected handler independently enforces all required checks for every action it receives. This issue is fixed in version 0.4.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-104873</guid>
    </item>
    <item>
      <title>GHSA-fvww-7h3r-vfhp — LangGraph SDK custom auth silently ignores actions= on resource decorators</title>
      <link>https://db.gcve.eu/vuln/ghsa-fvww-7h3r-vfhp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: langgraph-sdk&lt;/p&gt;
&lt;p&gt;### Impact
_What kind of vulnerability is it? Who is impacted?_
`langgraph-sdk` incorrectly applies the `actions=` argument on resource-scoped authorization decorators, including `@auth.on.threads`, `@auth.on.assistants`, and `@auth.on.crons`.&lt;/p&gt;
&lt;p&gt;In affected versions, a decorator such as:&lt;/p&gt;
&lt;p&gt;```python
@auth.on.threads(actions=[&amp;#34;create&amp;#34;])
async def allow_thread_create(ctx, value):
    return None
```
intended to register a handler for selected actions instead registers that handler for every action on the resource. Because the resource-wide handler is selected before broader fallback handlers, authorization checks implemented in those fallback handlers may not run.&lt;/p&gt;
&lt;p&gt;An authenticated user may therefore be able to perform actions the application intended to deny, such as reading, updating, or deleting another user&amp;#39;s resource. Exploitability and impact depend on the affected handler&amp;#39;s behavior: deployments remain protected if that handler independently enforces the necessary action, ownership, or permission checks for every request it receives.&lt;/p&gt;
&lt;p&gt;Only Python deployments using `actions=` on the affected resource-scoped decorators are affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;0.4.4&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;No.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;N/A&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: langgraph-sdk&lt;/p&gt;
&lt;p&gt;### Impact
_What kind of vulnerability is it? Who is impacted?_
`langgraph-sdk` incorrectly applies the `actions=` argument on resource-scoped authorization decorators, including `@auth.on.threads`, `@auth.on.assistants`, and `@auth.on.crons`.&lt;/p&gt;
&lt;p&gt;In affected versions, a decorator such as:&lt;/p&gt;
&lt;p&gt;```python
@auth.on.threads(actions=[&amp;#34;create&amp;#34;])
async def allow_thread_create(ctx, value):
    return None
```
intended to register a handler for selected actions instead registers that handler for every action on the resource. Because the resource-wide handler is selected before broader fallback handlers, authorization checks implemented in those fallback handlers may not run.&lt;/p&gt;
&lt;p&gt;An authenticated user may therefore be able to perform actions the application intended to deny, such as reading, updating, or deleting another user&amp;#39;s resource. Exploitability and impact depend on the affected handler&amp;#39;s behavior: deployments remain protected if that handler independently enforces the necessary action, ownership, or permission checks for every request it receives.&lt;/p&gt;
&lt;p&gt;Only Python deployments using `actions=` on the affected resource-scoped decorators are affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;0.4.4&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;No.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;N/A&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-fvww-7h3r-vfhp</guid>
    </item>
  </channel>
</rss>
