Repository navigation
fix: constrain langsmith >=0.6.3 on Python >=3.10 to resolve CVE-2026-25528 - #25
Merged
John Kennedy (jkennedyvz) merged 1 commit intoFeb 25, 2026
Conversation
…-25528 langsmith >= 0.4.10, < 0.6.3 is vulnerable to SSRF via crafted tracing headers. langsmith >= 0.6.3 requires Python >= 3.10, so the constraint is split: >= 0.6.3 for Python >= 3.10, >= 0.3.45 for Python 3.9 (no patched release available for 3.9 upstream). Python >= 3.10 now resolves langsmith 0.7.6. Strategy C constraint; remove once langchain-core pulls in langsmith >= 0.6.3 directly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
John Kennedy (jkennedyvz)
enabled auto-merge (squash)
February 25, 2026 02:52
John Kennedy (jkennedyvz)
disabled auto-merge
February 25, 2026 02:52
John Kennedy (jkennedyvz)
deleted the
fix/security-alerts-langsmith-2026-02-24
branch
February 25, 2026 02:52
John Kennedy (jkennedyvz)
added a commit
that referenced
this pull request
Mar 1, 2026
## Summary Python 3.9 reached end-of-life on 2025-10-05. This PR removes it from the supported range. ## Changes - `pyproject.toml`: `python = ">=3.9,<4.0"` → `">=3.10,<4.0"` - `poetry.lock`: regenerated — 32 fewer lines as 3.9-only resolution paths are removed ## Notes - The CI matrix (`_test.yml`, `_lint.yml`, `_compile_integration_test.yml`, `_scheduled_test.yml`) already starts at 3.10 — no workflow changes needed. - Dropping 3.9 also unblocks a clean `langsmith >= 0.6.3` constraint (see PR #25, CVE-2026-25528) — that PR's split constraint for Python 3.9/3.10 can be simplified to an unconditional `>= 0.6.3` once this merges. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Security Alert Patch — medium severity
Resolves CVE-2026-25528 for Python >= 3.10 environments.
Package Updated
langsmith>=0.6.3>=3.10langsmith>=0.3.45<3.10CVE Details
CVE-2026-25528 (medium) —
langsmith >= 0.4.10, < 0.6.3: SSRF via craftedX-Forwarded-For/ tracing headers in the LangSmith Client SDK.Python 3.9 limitation
langsmith >= 0.6.3 requires Python >= 3.10. There is no patched release compatible with Python 3.9. The constraint is therefore split:
langsmith 0.7.6✓ patchedlangsmith 0.4.37— still vulnerable; no upstream fix availableThis constraint can be removed once
langchain-coreupdates its ownlangsmithlower bound to>= 0.6.3.Skipped (no patched version available)
docarrayCVE-2025-5150 (medium) — nofirst_patched_versionorjsonCVE-2025-67221 (medium) — nofirst_patched_versionlangchain-coreCVE-2026-26013 (low) — requires bumping to>= 1.2.11(pastlangchain-openai ^0.3compatibility boundary); warrants a separate ecosystem upgrade PRVerification
poetry lock)ruff check,ruff format --check)🤖 Submitted by langster-patch