LangChain4j
Filed as: Quarkus LangChain4j
Newest record 2026-10-11 · 3 distinct CVE ids · open in the explorer (the explorer matches the first product a record names, so it can list fewer)
Exploited or KEV-listed · 0
Records at severity 3–4 (exploitation confirmed by CISA, the vendor or reporting) and records flagged as listed in CISA KEV. The KEV flag is the classifier’s cisa-kev tag or a source on the KEV catalog; it is recorded when the collector sees the listing, so a missing flag does not mean a CVE is absent from the catalog.
No record for LangChain4j has confirmed exploitation or a KEV flag.
Disclosures by month · last 24 months
Disclosed CVEs, no confirmed exploitation · 3
- closed6.9LangChain4j CVE-2026-108748: Memory exhaustion in Quarkus LangChain4j chat-scopes WebSocket
Disclosed · since 11 Oct 2026 · CVE-2026-108748
AI - closed4.1LangChain4j CVE-2026-97869: LangChain4j deserialization flaw in AgenticScopeSerializer
Disclosed · since 25 Sep 2026 · CVE-2026-97869
AI - closed7.6LangChain4j SQL Injection in LangChain4j Embedding Stores
Disclosed · since 10 Jul 2026 · CVE-2026-55405
AI
Fix status and fixed versions are recorded when a source states them (each record’s page shows what is known); check the vendor’s own advisory before acting.