PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-97869 LangChain4j CVE debrief

A deserialization vulnerability exists in LangChain4j's AgenticScopeSerializer.fromJson function. This issue affects LangChain4j-agentic and requires an application to have enabled AgenticScope persistence, which is opt-in. An attacker who can already write to that store may exploit this vulnerability remotely with high complexity. The project maintainer has patched all maintained release lines, and upgrading to versions 1.5.3-beta11, 1.11.10-beta19, and 1.18.1-beta28 is advised.

Vendor
LangChain4j
Product
langchain4j-agentic
CVSS
LOW 1.2
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-25
Original CVE updated
2026-09-25
Advisory published
2026-09-25
Advisory updated
2026-09-25

Who should care

Defenders responsible for LangChain4j-agentic deployments, especially those with AgenticScope persistence enabled, should assess exposure and prioritize patching to prevent potential deserialization attacks.

Why it matters

CVE-2026-97869 is a deserialization vulnerability in LangChain4j's AgenticScopeSerializer.fromJson function, requiring high complexity to exploit. Defenders should verify exposure, prioritize patching, and monitor for compromise indicators.

  • Verify if applications use the affected LangChain4j-agentic component with AgenticScope persistence enabled.
  • Assess network accessibility and potential exposure of the component.
  • Prioritize patching to prevent potential deserialization attacks.
  • Monitor for indicators of compromise related to this vulnerability.

Technical summary

The AgenticScopeSerializer.fromJson function in LangChain4j's LangChain4j-agentic component is vulnerable to deserialization attacks. This requires the application to have AgenticScope persistence enabled and an attacker who can write to that store. The attack complexity is rated as high. Defenders should verify if their applications use the affected LangChain4j-agentic component with AgenticScope persistence enabled and assess exposure based on the component's configuration and network accessibility. Upgrading to versions 1.5.3-beta11, 1.11.10-beta19, and 1.18.1-beta28 is advised to resolve this issue.

Defensive priority

Defenders should prioritize verifying if their applications use the affected LangChain4j-agentic component with AgenticScope persistence enabled and assess exposure based on the component's configuration and network accessibility.

Recommended defensive actions

  • Verify if the LangChain4j-agentic component is used with AgenticScope persistence enabled in your applications.
  • Assess the network accessibility of the affected component and potential exposure.
  • Upgrade to versions 1.5.3-beta11, 1.11.10-beta19, and 1.18.1-beta28 or later.
  • Monitor for any indicators of compromise related to this vulnerability.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and the patches available. However, the exact scope of affected applications and the number of potential victims are not specified.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-97869 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-97869

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-97869 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-97869

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.