LangChain4j
Filed as: Quarkus LangChain4j
Records
3
Disclosed CVEs
3
Exploited (sev 3–4)
0
CISA KEV flagged
0
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)
Patch now: confirmed exploitation or KEV · 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
█ ██
Nov ’243 disclosed · peak 1 in Jul ’26Oct ’26
Disclosed CVEs, no confirmed exploitation · 3
- 2026-10-11CVE-2026-108748CVE-2026-108748: Memory exhaustion in Quarkus LangChain4j chat-scopes WebSocket2 Disclosedlangchain4j · denial-of-service
- 2026-09-25CVE-2026-97869CVE-2026-97869: LangChain4j deserialization flaw in AgenticScopeSerializer2 Disclosedlangchain4j · deserialization
- 2026-07-10
This page lists what has been reported, not what to do about it. Versions and fixes are in each linked advisory; check the vendor’s own advisory before acting.