Skip to content

Fix GHSA-pjwx-r37v-7724 / CVE-2026-44843: bump langchain-core constraint to >=1.3.3 - #272

Closed
EvanderDS (EvanderDS) wants to merge 1 commit into
microsoft:mainfrom
EvanderDS:s360-fix/langchain-core-cve-mvs2023
Closed

Fix GHSA-pjwx-r37v-7724 / CVE-2026-44843: bump langchain-core constraint to >=1.3.3#272
EvanderDS (EvanderDS) wants to merge 1 commit into
microsoft:mainfrom
EvanderDS:s360-fix/langchain-core-cve-mvs2023

Conversation

@EvanderDS

@EvanderDS EvanderDS (EvanderDS) commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes a known vulnerability in the langchain-core dependency by bumping the centralized constraint in root pyproject.toml's [tool.uv] constraint-dependencies from >=0.1.0 to >=1.3.3 (no upper bound, matching the other unbounded AI-framework constraints in the same block).

CVE fixed

GHSA-pjwx-r37v-7724 / CVE-2026-44843 - LangChain unsafe deserialization of attacker-controlled objects through overly broad load() allowlists (affects RunnableWithMessageHistory, astream_log(), astream_events(v1), and related serialization/deserialization round-trips). The previously-locked langchain-core 1.2.28 fell inside the vulnerable >=1.0.0,<=1.3.2 range. 1.3.3 is the first patched 1.x release; the resolver picked up 1.6.2.

Local verification (this branch)

  • uv lock: resolves clean (langchain-core 1.2.28 -> 1.6.2)
  • uv sync --locked --all-extras --dev: clean
  • tox -e verify-constraints: PASS (this repo enforces centralized version constraints only in root pyproject.toml)
  • tox -e lint: PASS
  • tox -e format: PASS
  • tox -e py312: 800 passed, 3 skipped, 9 deselected, 0 failed (full suite, including the langchain observability extension's own 10 tests, all passing against the new version)

Reviewers

Requested review from dbezic, rbrighenti, DheerajPannala (same reviewers as the sibling google-adk security fix, #269).

This PR description was drafted with AI assistance. Please review carefully before merging.

…int to >=1.3.3

Fixes unsafe deserialization of attacker-controlled objects through overly
broad load() allowlists in RunnableWithMessageHistory, astream_log(), and
astream_events(v1). The previously-locked langchain-core 1.2.28 fell inside
the vulnerable >=1.0.0,<=1.3.2 range; 1.3.3 is the first patched 1.x release.
Resolver picked langchain-core 1.6.2.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@EvanderDS
EvanderDS (EvanderDS) requested a review from a team as a code owner September 9, 2026 11:12
Copilot AI lite review requested due to automatic review settings September 9, 2026 11:12
@EvanderDS

Copy link
Copy Markdown
Contributor Author

dbezic (@dbezic) Rick Brighenti (@rbrighenti) Krishnadheeraj (@DheerajPannala) could one of you review/approve? (submitted from a fork so I can't formally request review — flagging directly instead, same as #269/#285.) Note: if this repo's integration/secret-dependent CI checks fail on a fork PR, that's the known fork-secrets limitation (pull_request workflows from forks don't get repo secrets), not a problem from this dependency bump — the unit suite (tox -e py312, 800 passed) already covers it locally.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The change is a targeted constraint bump with clear security justification and no additional code-path modifications introduced in the PR diff.

Pull request overview

Updates the centralized uv dependency constraints to remediate GHSA-pjwx-r37v-7724 / CVE-2026-44843 by requiring a patched langchain-core version in the root workspace constraints.

Changes:

  • Bumped the root constraint-dependencies entry for langchain-core from >= 0.1.0 to >= 1.3.3.
  • Added inline rationale/comments documenting the CVE impact range and why the constraint remains unbounded.
File summaries
File Description
pyproject.toml Raises the centralized langchain-core minimum version to a patched release and documents the security rationale.
Review details
  • Files reviewed: 1/2 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants