langchain4j-aideepin before 3.31.0 IDOR via GET /character/{uuid}
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 3.31.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.31.0.
- Exploitation15/40CISA rates a proof of concept as public
- Exposure3/25Reachable over the network · Data gap: No advisory context yet
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity6/10CVSS 6.0
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 43 if advisories confirm default setups are exposed
CVE-2026-121938 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.0 (medium) and affects langchain4j-aideepin; fixed in 3.31.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 24/100 · provisional
- Fix
- Fixed in 3.31.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
langchain4j-aideepin versions before 3.31.0 contain an insecure direct object reference flaw that lets a logged-in user remotely read other users' character-chat conversations, including their questions, AI answers, and attachment and audio URLs, by requesting the character's UUID through the GET /character/{uuid} endpoint. No user interaction is needed, though the attacker must hold a valid account.
Read the original description
langchain4j-aideepin before 3.31.0 contains an insecure direct object reference vulnerability that allows authenticated users to read other users' character-chat conversations by supplying their character uuid. Attackers can request GET /character/{uuid}, which CharacterService.detail resolves without an ownership check, to obtain victims' questions, AI answers, and attachment and audio URLs.
What to do
Upgrade to a fixed version: 3.31.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- moyangzhan langchain4j-aideepin
fixed in 3.31.0
Evidence 7
- Patch
- Patch
- Exploit
- Report
- Repository
Show all 7 sourcesShow fewer sources
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121938
Is CVE-2026-121938 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-121938?
langchain4j-aideepin: before 3.31.0.Source: cve.now feed data
How do I fix CVE-2026-121938?
Upgrade to a fixed version: 3.31.0.Source: cve.now feed data