Security Deep Dive
langchain
Security posture and CVE patch evidence from tracked releases.
15 critical dependency CVEs affects langchain-deepseek==1.1.0.
Audit transitive dependencies; consider upgrading or pinning replacements.
— Signed
— SLSA
— SBOM
✗ Security policy
Weekly cadence · 0d median
Active maintainer
Trust Signals — 2 of 9 Present
Evidence already collected from releases and repository metadata.
2/9
Present
Signed releases
Unknown
Latest release artifact signature
Latest release
—
SLSA provenance
Unknown
Attestation predicate level
Latest release
—
SBOM published
Unknown
GitHub SBOM API
Latest release
—
SECURITY.md
Absent
GitHub repository metadata
Repository policy
Checked: 23d ago
Release cadence: weekly
Present
0d median over recent releases
Release history
Latest release: today
Maintainer active
Present
Recent commit activity
Repository
Last commit: 2d ago
Checksums (SHA256SUMS)
Not active yet
SHA256SUMS or equivalent
Release asset
Latest release: today
GitHub Actions attestation
Not active yet
actions/attest-build-provenance
Workflow file
Latest release: today
Signing assets
Not active yet
.sig, .crt, cosign.pub, or similar
Release asset
Latest release: today
4.3/10
Security Score
6.3/10
Scorecard
Dependency Exposure
106 transitive dependency
CVEs found in the latest SBOM.
15 critical.
Security Score
A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.
epss
0.25 / 0.5
No EPSS data
freshness
1.00 / 1.0
Up to date
scorecard
2.52 / 4.0
Score 6.3/10
cve health
0.00 / 2.5
⚠ No direct scan — 15c/32h transitive CVEs
patch speed
0.50 / 0.5
⚠ Estimated — no CVE patch history
kev exposure
1.50 / 1.5
No KEV exposure
supply chain risk
-1.50 / 10.0
Risk 100.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
direct cves: clear
cve scan: estimated
Release responsiveness
release responsiveness
10.0
5%
patch speed days: no_history
Dependency exposure
dependency exposure
0.0
10%
supply chain risk: 100.0
transitive cves: 15c/32h
Provenance trust
provenance trust
6.3
40%
scorecard score: 6.3
openssf badge: none
Maintainer health
maintainer health
10.0
10%
activity freshness: 0d
Operational risk
operational risk
8.5
10%
kev exposure: clear
epss max: none
How is this calculated?
The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.
Supply Chain Risk
Risk 100.0/100
15
Transitive critical CVEs
0
KEV-transitive CVEs
47%
Dependency freshness
Scorecard
Scorecard 6.3/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 10 | 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10 |
| Code-Review | 1 | Found 3/26 approved changesets -- score normalized to 1 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10 | no binaries found in the repo |
| License | 10 | license file detected |
| Fuzzing | 0 | project is not fuzzed |
| Security-Policy | 10 | security policy file detected |
| Branch-Protection | 3 | branch protection is not maximal on development and all release branches |
| Pinned-Dependencies | 8 | dependency not pinned by hash detected -- score normalized to 8 |
| Signed-Releases | -1 | no releases found |
| Packaging | 10 | packaging workflow detected |
| SAST | 9 | SAST tool is not run on all commits -- score normalized to 9 |
OpenSSF Badge
OpenSSF none
Badge indicates adherence to open-source best practices.
Dependency Vulnerabilities
2448 dependencies scanned
View full dependency list →
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
15
High
32
Medium
42
Low
17
Unknown
0
Critical
15
High
32
Medium
42
Low
17
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2023-29374 | critical | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-32785 | critical | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-34540 | critical | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-34541 | critical | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-36095 | critical | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-36188 | critical | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-36258 | critical | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-36281 | critical | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-38860 | critical | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-38896 | critical | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-39631 | critical | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-39659 | critical | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-6730 | critical | — | transformers | — | langchain==1.3.0a2 |
| CVE-2025-14009 | critical | — | nltk | — | langchain==1.3.0a2 |
| CVE-2025-43859 | critical | — | h11 | 0.14.0 | langchain==1.3.0a2 |
| CVE-2019-14751 | high | — | nltk | — | langchain==1.3.0a2 |
| CVE-2021-3828 | high | — | nltk | — | langchain==1.3.0a2 |
| CVE-2021-3842 | high | — | nltk | — | langchain==1.3.0a2 |
| CVE-2021-43854 | high | — | nltk | — | langchain==1.3.0a2 |
| CVE-2023-32786 | high | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-36189 | high | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-46229 | high | — | langchain | — | langchain==1.3.0a2 |
| CVE-2023-7018 | high | — | transformers | — | langchain==1.3.0a2 |
| CVE-2024-11392 | high | — | transformers | — | langchain==1.3.0a2 |
| CVE-2024-11393 | high | — | transformers | — | langchain==1.3.0a2 |
| CVE-2024-11394 | high | — | transformers | — | langchain==1.3.0a2 |
| CVE-2024-39705 | high | — | nltk | — | langchain==1.3.0a2 |
| CVE-2025-4565 | high | — | protobuf | 4.25.5 | langchain==1.3.0a2 |
| CVE-2025-47273 | high | — | setuptools | 75.3.0 | langchain==1.3.0a2 |
| CVE-2025-62727 | high | — | starlette | 0.41.2 | langchain==1.3.0a2 |
| CVE-2025-66418 | high | — | urllib3 | 2.2.3 | langchain==1.3.0a2 |
| CVE-2025-66471 | high | — | urllib3 | 2.2.3 | langchain==1.3.0a2 |
| CVE-2025-67221 | high | — | orjson | 3.10.10 | langchain==1.3.0a2 |
| CVE-2025-69223 | high | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2026-0846 | high | — | nltk | — | langchain==1.3.0a2 |
| CVE-2026-0847 | high | — | nltk | — | langchain==1.3.0a2 |
| CVE-2026-0994 | high | — | protobuf | 4.25.5 | langchain==1.3.0a2 |
| CVE-2026-21441 | high | — | urllib3 | 2.2.3 | langchain==1.3.0a2 |
| CVE-2026-23490 | high | — | pyasn1 | 0.6.1 | langchain==1.3.0a2 |
| CVE-2026-25990 | high | — | pillow | 11.1.0 | langchain==1.3.0a2 |
| CVE-2026-30922 | high | — | pyasn1 | 0.6.1 | langchain==1.3.0a2 |
| CVE-2026-33079 | high | — | mistune | 3.1.4 | langchain==1.3.0a2 |
| CVE-2026-33231 | high | — | nltk | — | langchain==1.3.0a2 |
| CVE-2026-33236 | high | — | nltk | — | langchain==1.3.0a2 |
| CVE-2026-40192 | high | — | pillow | 11.1.0 | langchain==1.3.0a2 |
| CVE-2026-41066 | high | — | lxml | — | langchain==1.3.0a2 |
| CVE-2026-42311 | high | — | pillow | 11.1.0 | langchain==1.3.0a2 |
| CVE-2014-3146 | medium | — | lxml | — | langchain==1.3.0a2 |
| CVE-2018-19787 | medium | — | lxml | — | langchain==1.3.0a2 |
| CVE-2020-27783 | medium | — | lxml | — | langchain==1.3.0a2 |
| CVE-2021-28957 | medium | — | lxml | — | langchain==1.3.0a2 |
| CVE-2021-43818 | medium | — | lxml | — | langchain==1.3.0a2 |
| CVE-2022-2309 | medium | — | lxml | — | langchain==1.3.0a2 |
| CVE-2023-2800 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2024-12720 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2024-2965 | medium | — | langchain | — | langchain==1.3.0a2 |
| CVE-2024-3571 | medium | — | langchain | — | langchain==1.3.0a2 |
| CVE-2024-47081 | medium | — | requests | 2.32.3 | langchain==1.3.0a2 |
| CVE-2025-1194 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2025-2099 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2025-3262 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2025-3263 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2025-3264 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2025-3933 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2025-50181 | medium | — | urllib3 | 2.2.3 | langchain==1.3.0a2 |
| CVE-2025-50182 | medium | — | urllib3 | 2.2.3 | langchain==1.3.0a2 |
| CVE-2025-5197 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2025-54121 | medium | — | starlette | 0.41.2 | langchain==1.3.0a2 |
| CVE-2025-6051 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2025-6638 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2025-68146 | medium | — | filelock | 3.16.1 | langchain==1.3.0a2 |
| CVE-2025-6921 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2025-69227 | medium | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2025-69228 | medium | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2025-69229 | medium | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2025-71176 | medium | — | pytest | 7.4.4 | langchain==1.3.0a2 |
| CVE-2026-1839 | medium | — | transformers | — | langchain==1.3.0a2 |
| CVE-2026-22701 | medium | — | filelock | 3.16.1 | langchain==1.3.0a2 |
| CVE-2026-22815 | medium | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2026-25645 | medium | — | requests | 2.32.3 | langchain==1.3.0a2 |
| CVE-2026-28684 | medium | — | python-dotenv | 1.0.1 | langchain==1.3.0a2 |
| CVE-2026-33230 | medium | — | nltk | — | langchain==1.3.0a2 |
| CVE-2026-34515 | medium | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2026-34516 | medium | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2026-34525 | medium | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2026-41182 | medium | — | langsmith | 0.1.139 | langchain==1.3.0a2 |
| CVE-2026-42308 | medium | — | pillow | 11.1.0 | langchain==1.3.0a2 |
| CVE-2026-42310 | medium | — | pillow | 11.1.0 | langchain==1.3.0a2 |
| GHSA-rf74-v2fm-23pw | medium | — | nltk | — | langchain==1.3.0a2 |
| CVE-2024-0243 | low | — | langchain | — | langchain==1.3.0a2 |
| CVE-2024-28088 | low | — | langchain | — | langchain==1.3.0a2 |
| CVE-2024-3568 | low | — | transformers | — | langchain==1.3.0a2 |
| CVE-2024-8309 | low | — | langchain | — | langchain==1.3.0a2 |
| CVE-2025-3777 | low | — | transformers | — | langchain==1.3.0a2 |
| CVE-2025-53643 | low | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2025-69224 | low | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2025-69225 | low | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2025-69226 | low | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2025-69230 | low | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2026-34513 | low | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2026-34514 | low | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2026-34517 | low | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2026-34518 | low | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2026-34519 | low | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2026-34520 | low | — | aiohttp | 3.11.11 | langchain==1.3.0a2 |
| CVE-2026-4539 | low | — | pygments | 2.18.0 | langchain==1.3.0a2 |
Showing 106 of 106