Security Deep Dive
DB-GPT
Security posture and CVE patch evidence from tracked releases.
6 critical dependency CVEs affects v0.8.1.
Audit transitive dependencies; consider upgrading or pinning replacements.
Versions by Severity
CVEs are attributed to tracked releases published before the patch release.
| Version | Published | C | H | M | L | KEV | Notes |
|---|---|---|---|---|---|---|---|
| v0.8.1 | 2026-06-18 | — | — | — | — | — | |
| v0.8.0 | 2026-03-27 | 1 | 2 | — | — | KEV 3 |
—
|
| v0.7.5 | 2026-02-11 | 1 | 2 | — | — | KEV 3 |
—
|
Trust Signals — 2 of 9 Present
Evidence already collected from releases and repository metadata.
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.00 / 0.5
Max EPSS 0.930
freshness
1.00 / 1.0
3d stale
scorecard
2.00 / 4.0
⚠ Estimated — not yet collected
cve health
0.00 / 2.5
⚠ No direct scan — 36c/165h transitive CVEs
patch speed
0.50 / 0.5
⚠ Estimated — no CVE patch history
kev exposure
-1.50 / 1.5
KEV exposure detected
supply chain risk
-1.50 / 10.0
Risk 100.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
0.0
10%
Provenance trust
provenance trust
5.0
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
0.0
10%
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/100OpenSSF Badge
Badge indicates adherence to open-source best practices.
CVE Patch History
Tracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.
CVEs Patched by Year
| CVE | Severity | EPSS | Disclosed | Fixed in | Days to fix | vs Ecosystem Median | KEV |
|---|---|---|---|---|---|---|---|
| CVE-2022-33891 | HIGH | 99%ile | — | v0.8.1 | — | — | KEV |
| CVE-2026-42208 | CRITICAL | 99%ile | — | v0.8.1 | — | — | KEV |
| CVE-2026-42271 | HIGH | 99%ile | — | v0.8.1 | — | — | KEV |
KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
6
High
23
Medium
16
Low
5
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2024-9052 | critical | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-29783 | critical | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-32444 | critical | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-47277 | critical | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-68664 | critical | — | langchain-core | 0.3.51 | v0.8.1 |
| GHSA-ggpf-24jw-3fcw | critical | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2024-4340 | high | — | sqlparse | 0.4.4 | v0.8.1 |
| CVE-2024-52798 | high | — | path-to-regexp | 0.1.7 | v0.8.1 |
| CVE-2025-30165 | high | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-30202 | high | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-48956 | high | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-57809 | high | — | xgrammar | 0.1.18 | v0.8.1 |
| CVE-2025-59425 | high | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-62372 | high | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-6242 | high | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-62611 | high | — | aiomysql | 0.2.0 | v0.8.1 |
| CVE-2025-65106 | high | — | langchain-core | 0.3.51 | v0.8.1 |
| CVE-2025-66448 | high | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-6984 | high | — | langchain-community | 0.3.21 | v0.8.1 |
| CVE-2025-6985 | high | — | langchain-text-splitters | 0.3.8 | v0.8.1 |
| CVE-2026-1260 | high | — | sentencepiece | 0.2.0 | v0.8.1 |
| CVE-2026-23490 | high | — | pyasn1 | 0.6.1 | v0.8.1 |
| CVE-2026-24486 | high | — | python-multipart | 0.0.20 | v0.8.1 |
| CVE-2026-24779 | high | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2026-25048 | high | — | xgrammar | 0.1.18 | v0.8.1 |
| CVE-2026-30922 | high | — | pyasn1 | 0.6.1 | v0.8.1 |
| CVE-2026-34070 | high | — | langchain-core | 0.3.51 | v0.8.1 |
| CVE-2026-42561 | high | — | python-multipart | 0.0.20 | v0.8.1 |
| CVE-2026-4867 | high | — | path-to-regexp | 0.1.7 | v0.8.1 |
| CVE-2025-29770 | medium | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-46722 | medium | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-48887 | medium | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-61620 | medium | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2025-62426 | medium | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2026-22773 | medium | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2026-34755 | medium | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2026-34756 | medium | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2026-40087 | medium | — | langchain-core | 0.3.51 | v0.8.1 |
| CVE-2026-40347 | medium | — | python-multipart | 0.0.20 | v0.8.1 |
| CVE-2026-41182 | medium | — | langsmith | 0.3.31 | v0.8.1 |
| CVE-2026-41481 | medium | — | langchain-text-splitters | 0.3.8 | v0.8.1 |
| CVE-2026-44222 | medium | — | vllm | 0.7.2 | v0.8.1 |
| GHSA-27jp-wm6q-gp25 | medium | — | sqlparse | 0.4.4 | v0.8.1 |
| GHSA-hf3c-wxg2-49q9 | medium | — | vllm | 0.7.2 | v0.8.1 |
| GHSA-j828-28rj-hfhp | medium | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2024-47764 | low | — | cookie | 0.5.0 | v0.8.1 |
| CVE-2025-46570 | low | — | vllm | 0.7.2 | v0.8.1 |
| CVE-2026-26013 | low | — | langchain-core | 0.3.51 | v0.8.1 |
| CVE-2026-41488 | low | — | langchain-openai | 0.3.12 | v0.8.1 |
| CVE-2026-7141 | low | — | vllm | 0.7.2 | v0.8.1 |
Showing 50 of 414