PR Custody

fix(security): pin langchain-core to >=0.3.81 (Socket.dev critical CVE)

@zen-agentchecks n/achecks…zen/socket-fix-langchain-core-7jq6ep → next2 files · +37 −3updated 3w ago

▸Description· 2 comments · 1 noise

Why

Socket.dev flagged a critical vulnerability in langchain-core@0.3.72 (which the lockfile resolves transitively via langchain_aws, langgraph, and langchain-google-vertexai):

Socket alert	CVE	GHSA	Severity	Patched in
`SOCKET-COMPOSIO-1055`	`CVE-2025-68664`	`GHSA-c67j-w6g6-q2cm`	Critical	`0.3.81` (and `1.2.5` on the 1.x line)

The advisory describes a deserialization-injection vulnerability that can be used to exfiltrate secrets when untrusted LangChain payloads are loaded.

What

Add a direct pin langchain-core>=0.3.81,<0.4 in cortex/pyproject.toml.
Regenerate uv.lock. langchain-core resolves from 0.3.72 -> 0.3.86.
Both langchain_aws@0.2.13 (>=0.3.27,<0.4) and langgraph@0.3.34 (>=0.1,<0.4) already allow this range, so no peer bumps required.

How to Test

uv lock regenerated cleanly — confirms peers accept 0.3.86.
uv sync installs the new versions.
python -c "import langchain_core; print(langchain_core.__version__)" -> 0.3.86.
make chk -> all checks passed (ruff format, ruff check, import sort, pyrefly type check — 0 errors).

Pre-Review Checklist

I have self-reviewed this PR

Notes

Lowest-risk bump available: 0.3.x patch line stays within the langchain_aws / langgraph constraints, so no transitive peer upgrades are pulled in. Staying off the 1.x line keeps the existing langchain ecosystem stable.

Origin: cron-f7c85f82906b / zen-cron-6352a6575b74 Triggered by: saransh@composio.dev | Source: Socket.dev Vulnerability Auto-Fix Session: https://zen-api-production-4c98.up.railway.app/dashboard/#/chat/zen-cron-6352a6575b74

@zen-agent3w ago

CI status update

Check	Status	Notes
`Lint - Integrator`	✅ success	clean
`Check File Size`	✅ success	clean
`PR #1431` (CodeQL)	✅ success	clean
`Unit Tests - Integrator`	❌ failure	pre-existing — same two tests (`tests/unit/test_common/test_composio_client.py::TestComposioAPIClient::test_get_auth_data[production]`, `test_validators.py::TestValidateConnectionId::test_valid_connection_id_passes[production]`) fail on `next` baseline with the same `403 Forbidden` from `/api/v3/admin/connections/...` (verified against the last run on `next` at SHA `6a20828f`). Not caused by this PR.
`secrets-detection.yml`	❌ failure	pre-existing — same workflow failed on `next` (and on recently merged PR #1414, which still merged). Not caused by this PR.
`Integration Tests`	⏳ running	(in progress at comment time)

The lockfile-only change (langchain-core 0.3.72 → 0.3.86) cannot plausibly produce a 403 on an admin endpoint. Both failures are infra/credential issues that pre-date this PR.

Origin: cron-f7c85f82906b / zen-cron-6352a6575b74

@zen-agent3w ago

Final status update (post-PR lifecycle complete)

Step	Result
Local build/install

▸ 1 bot/status comment hidden

@socket-security[bot]3w ago

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

View full report

loading diff…

@zen-agent3w ago

CI status update

Check	Status	Notes
`Lint - Integrator`	✅ success	clean
`Check File Size`	✅ success	clean
`PR #1431` (CodeQL)	✅ success	clean
`Unit Tests - Integrator`	❌ failure	pre-existing — same two tests (`tests/unit/test_common/test_composio_client.py::TestComposioAPIClient::test_get_auth_data[production]`, `test_validators.py::TestValidateConnectionId::test_valid_connection_id_passes[production]`) fail on `next` baseline with the same `403 Forbidden` from `/api/v3/admin/connections/...` (verified against the last run on `next` at SHA `6a20828f`). Not caused by this PR.
`secrets-detection.yml`	❌ failure	pre-existing — same workflow failed on `next` (and on recently merged PR #1414, which still merged). Not caused by this PR.
`Integration Tests`	⏳ running	(in progress at comment time)

The lockfile-only change (langchain-core 0.3.72 → 0.3.86) cannot plausibly produce a 403 on an admin endpoint. Both failures are infra/credential issues that pre-date this PR.

Origin: cron-f7c85f82906b / zen-cron-6352a6575b74