https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 20 Oct 2026 13:12:55 +0000 https://db.gcve.eu/vuln/brew-langgraph-cli-cve-2026-104873 <p><strong>Affected:</strong> Homebrew: langgraph-cli</p> <p>### 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`.</p> <p>In affected versions, a decorator such as:</p> <p>```python @auth.on.threads(actions=[&#34;create&#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.</p> <p>An authenticated user may therefore be able to perform actions the application intended to deny, such as reading, updating, or deleting another user&#39;s resource. Exploitability and impact depend on the affected handler&#39;s behavior: deployments remain protected if that handler independently enforces the necessary action, ownership, or permission checks for every request it receives.</p> <p>Only Python deployments using `actions=` on the affected resource-scoped decorators are affected.</p> <p>### Patches</p> <p>0.4.4</p> <p>### Workarounds</p> <p>No.</p> <p>### References</p> <p>N/A</p> <p><strong>Affected:</strong> Homebrew: langgraph-cli</p> <p>### 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`.</p> <p>In affected versions, a decorator such as:</p> <p>```python @auth.on.threads(actions=[&#34;create&#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.</p> <p>An authenticated user may therefore be able to perform actions the application intended to deny, such as reading, updating, or deleting another user&#39;s resource. Exploitability and impact depend on the affected handler&#39;s behavior: deployments remain protected if that handler independently enforces the necessary action, ownership, or permission checks for every request it receives.</p> <p>Only Python deployments using `actions=` on the affected resource-scoped decorators are affected.</p> <p>### Patches</p> <p>0.4.4</p> <p>### Workarounds</p> <p>No.</p> <p>### References</p> <p>N/A</p> https://db.gcve.eu/vuln/brew-langgraph-cli-cve-2026-104873 https://db.gcve.eu/vuln/fkie_cve-2026-104873 <p>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&#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.</p> <p>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&#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.</p> https://db.gcve.eu/vuln/fkie_cve-2026-104873 https://db.gcve.eu/vuln/ghsa-fvww-7h3r-vfhp <p><strong>Affected:</strong> PyPI: langgraph-sdk</p> <p>### 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`.</p> <p>In affected versions, a decorator such as:</p> <p>```python @auth.on.threads(actions=[&#34;create&#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.</p> <p>An authenticated user may therefore be able to perform actions the application intended to deny, such as reading, updating, or deleting another user&#39;s resource. Exploitability and impact depend on the affected handler&#39;s behavior: deployments remain protected if that handler independently enforces the necessary action, ownership, or permission checks for every request it receives.</p> <p>Only Python deployments using `actions=` on the affected resource-scoped decorators are affected.</p> <p>### Patches</p> <p>0.4.4</p> <p>### Workarounds</p> <p>No.</p> <p>### References</p> <p>N/A</p> <p><strong>Affected:</strong> PyPI: langgraph-sdk</p> <p>### 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`.</p> <p>In affected versions, a decorator such as:</p> <p>```python @auth.on.threads(actions=[&#34;create&#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.</p> <p>An authenticated user may therefore be able to perform actions the application intended to deny, such as reading, updating, or deleting another user&#39;s resource. Exploitability and impact depend on the affected handler&#39;s behavior: deployments remain protected if that handler independently enforces the necessary action, ownership, or permission checks for every request it receives.</p> <p>Only Python deployments using `actions=` on the affected resource-scoped decorators are affected.</p> <p>### Patches</p> <p>0.4.4</p> <p>### Workarounds</p> <p>No.</p> <p>### References</p> <p>N/A</p> https://db.gcve.eu/vuln/ghsa-fvww-7h3r-vfhp https://db.gcve.eu/vuln/pysec-2026-4240 <p><strong>Affected:</strong> PyPI: langgraph-sdk</p> <p>### 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`.</p> <p>In affected versions, a decorator such as:</p> <p>```python @auth.on.threads(actions=[&#34;create&#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.</p> <p>An authenticated user may therefore be able to perform actions the application intended to deny, such as reading, updating, or deleting another user&#39;s resource. Exploitability and impact depend on the affected handler&#39;s behavior: deployments remain protected if that handler independently enforces the necessary action, ownership, or permission checks for every request it receives.</p> <p>Only Python deployments using `actions=` on the affected resource-scoped decorators are affected.</p> <p>### Patches</p> <p>0.4.4</p> <p>### Workarounds</p> <p>No.</p> <p>### References</p> <p>N/A</p> <p><strong>Affected:</strong> PyPI: langgraph-sdk</p> <p>### 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`.</p> <p>In affected versions, a decorator such as:</p> <p>```python @auth.on.threads(actions=[&#34;create&#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.</p> <p>An authenticated user may therefore be able to perform actions the application intended to deny, such as reading, updating, or deleting another user&#39;s resource. Exploitability and impact depend on the affected handler&#39;s behavior: deployments remain protected if that handler independently enforces the necessary action, ownership, or permission checks for every request it receives.</p> <p>Only Python deployments using `actions=` on the affected resource-scoped decorators are affected.</p> <p>### Patches</p> <p>0.4.4</p> <p>### Workarounds</p> <p>No.</p> <p>### References</p> <p>N/A</p> https://db.gcve.eu/vuln/pysec-2026-4240 https://db.gcve.eu/vuln/rhsa-2026:84734 <p>Cohere North AI: Cohere North AI: Arbitrary user information overwrite via incorrect access control Cohere North AI: Cohere North AI: Information disclosure via improper Origin header validation Cohere North AI: Cohere North AI: Information Leak via WebSocket Endpoint urllib3: urllib3 Streaming API improperly handles highly compressed data python-transformers: python-transformers: Arbitrary code execution due to overridden trust_remote_code setting fast-uri: fast-uri: URI authority bypass due to improper delimiter handling undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing python-pip: Path traversal via malicious entry point name in pip wheel installation allows arbitrary file overwrite urllib3: urllib3: Denial of Service via decompression bomb bypass with Brotli support org.eclipse.parsson/parsson: Eclipse Parsson: Denial of Service via uncontrolled resource consumption in JSON parsing undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy jetty-security: Eclipse Jetty: Authentication bypass via Digest authentication encoding collision jetty: Eclipse Jetty: Information disclosure due to retained HTTP/1.1 trailers across connections sqlite: SQLite: Arbitrary code execution via crafted FTS5 full-text search data sqlite: SQLite: Arbitrary code execution and crash via heap-based buffer overflow in FTS5 form-data: form-data: Form field override via CRLF injection undici: undici: Denial…</p> <p>Cohere North AI: Cohere North AI: Arbitrary user information overwrite via incorrect access control Cohere North AI: Cohere North AI: Information disclosure via improper Origin header validation Cohere North AI: Cohere North AI: Information Leak via WebSocket Endpoint urllib3: urllib3 Streaming API improperly handles highly compressed data python-transformers: python-transformers: Arbitrary code execution due to overridden trust_remote_code setting fast-uri: fast-uri: URI authority bypass due to improper delimiter handling undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing python-pip: Path traversal via malicious entry point name in pip wheel installation allows arbitrary file overwrite urllib3: urllib3: Denial of Service via decompression bomb bypass with Brotli support org.eclipse.parsson/parsson: Eclipse Parsson: Denial of Service via uncontrolled resource consumption in JSON parsing undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy jetty-security: Eclipse Jetty: Authentication bypass via Digest authentication encoding collision jetty: Eclipse Jetty: Information disclosure due to retained HTTP/1.1 trailers across connections sqlite: SQLite: Arbitrary code execution via crafted FTS5 full-text search data sqlite: SQLite: Arbitrary code execution and crash via heap-based buffer overflow in FTS5 form-data: form-data: Form field override via CRLF injection undici: undici: Denial…</p> https://db.gcve.eu/vuln/rhsa-2026:84734