langchain4j-aideepin before 3.31.0 contains an insecure direct object reference vulnerability that allows
Source GCVE Database
Not known to be exploited · CVSS 6.0 Medium : upgrade to 3.31.0 when convenient.
Data as of 4 Nov 2026, 16:43 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.0 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.3 |
- Patch
- Available – fixed in 3.31.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Upgrade langchain4j-aideepin to 3.31.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| moyangzhanlangchain4j-aideepin | Affected
| Fixed in
|
GitHublangchain4j-aideepinpkg:github/langchain4j-aideepinOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fixed version 3.31.0 or later is implied but not explicitly confirmed in the provided data. If you cannot patch yet, restrict access to the /character/{uuid} endpoint to ensure proper ownership verification is enforced. Avoid sharing character UUIDs publicly and monitor for unauthorized access attempts.
Description
An insecure direct object reference (IDOR) vulnerability exists in langchain4j-aideepin versions before 3.31.0. Authenticated users can access other users' character-chat conversations by supplying the target user's character UUID. The vulnerability arises because the CharacterService.detail endpoint does not perform ownership checks on GET /character/{uuid} requests, exposing sensitive conversation data including questions, AI responses, and media URLs.
References
- nvd.nist.gov/vuln/detail/CVE-2026-121938 (opens in a new tab)
- github.com/moyangzhan/langchain4j-aideepin/issues/116 (opens in a new tab)
- github.com/moyangzhan/langchain4j-aideepin/pull/117 (opens in a new tab)
- github.com/moyangzhan/langchain4j-aideepin/commit/9b2fee6b66836a0efd5599cfcddd05b80b05ca93 (opens in a new tab)
- github.com/moyangzhan/langchain4j-aideepin/blob/v3.30.0/server/adi-common/src/main/java/com/moyz/adi/common/service/CharacterService.java (opens in a new tab)
- hackmd.io/@hieuPenguinnn/langchain4j-aideepin-character-conversation-cross-user-idor (opens in a new tab)
- vulncheck.com/advisories/langchain4j-aideepin-before-3.31.0-idor-via-get-character-uuid (opens in a new tab)