Security: 2 CVE fixes for NSPECT-S62Q-PZUD#684
Draft
nv-rag-cve-bot[bot] wants to merge 4 commits into
Draft
Conversation
added 2 commits
June 16, 2026 02:32
….1 → >=1.3.3 (UNVERIFIED) pyproject.toml: langchain lower bound 1.3.1 → 1.3.3 (fixes CVE-2026-44843, Critical). uv.lock regenerated: langchain 1.3.1→1.3.9, langchain-core 1.4.0→1.4.7, langgraph 1.2.1→1.2.5. Unit pin guard added; full CI validation pending (pipeline mode, Track B — OSV feed stale). Refs: NSPECT-S62Q-PZUD Generated-by: agentic-cve-fix
…5.0.4 → 5.0.6 (UNVERIFIED) frontend/package.json: pnpm.overrides forces brace-expansion@5.0.4 → 5.0.6 (High). pnpm-lock.yaml will regenerate in CI; scanner confirmation pending (pnpm unavailable locally). Track B — lockfile not yet updated; CI enforces the override on next pnpm install. Refs: NSPECT-S62Q-PZUD Generated-by: agentic-cve-fix
…e streaming CI iteration 2 revealed Test 69, Test 64, Test 153 timing out at 300s. Root cause: langchain>=1.3.3 resolved to 1.3.7, which required langgraph>=1.2.4, and uv picked langgraph 1.2.5. langgraph 1.2.5 requires langchain-core>=1.4.7, and langchain-core 1.4.7 breaks streaming (LLM response returns empty/no choices). Fix: pin langgraph>=1.2.4,<1.2.5 and langchain-core>=1.4.0,<1.4.1 in override-dependencies, restoring the same langchain-core 1.4.0 that the develop branch baseline uses (confirmed passing CI run 27008380332). The CVE-2026-44843 fix (langchain>=1.3.3) remains intact — resolved to 1.3.7. Co-Authored-By: Claude <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
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: 2 CVE fixes for NSPECT-S62Q-PZUD
nSpect program: NSPECT-S62Q-PZUD (collection → children NSPECT-UV6I-R3V9, NSPECT-O8B9-SHZ8)
Version scope: 26.05.2 (semver-latest non-EOL)
Track: B — RECOMMENDATION (UNVERIFIED) — OSV database stale for 2026 CVEs; nSpect advisory is authoritative
CVEs fixed
pyproject.toml:>=1.3.1→>=1.3.3,<1.3.8; uv override pins langgraph 1.2.4, langchain-core 1.4.0; uv.lock regenerated (langchain 1.3.7)frontend/package.jsonpnpm.overrides:"brace-expansion@5.0.4": "5.0.6"; pnpm-lock.yaml regeneratedFiles changed
pyproject.toml— langchain 1.3.1→1.3.7 (CVE fix); langgraph, langchain-core caps added to preserve streaming compatibilityuv.lock— regenerated (langchain 1.3.7, langchain-core 1.4.0, langgraph 1.2.4, langgraph-sdk 0.4.2)frontend/package.json— brace-expansion pnpm override addedfrontend/pnpm-lock.yaml— regenerated (brace-expansion 5.0.4→5.0.6 applied)tests/unit/test_security_dependency_pins.py—test_langchain_not_vulnerable_cve_2026_44843addedAlready-patched CVEs (confirmed, no change needed)
CVE-2025-65106, CVE-2025-68664 (langchain-core), CVE-2025-6984 (langchain-community), CVE-2026-45134 (langsmith)
CI iteration notes
ERR_PNPM_LOCKFILE_CONFIG_MISMATCHby regenerating pnpm-lock.yaml; Integration Tests RED (langchain-core 1.4.7 streaming regression)Validation
Generated by agentic-cve-fix skill — NSPECT-S62Q-PZUD — 2026-06-16
Track B: Both CVEs unverified by local scanner (OSV stale). nSpect advisory is authoritative. Verification occurs on post-merge nSpect rescan.