CVE-2026-97869: langchain4j LangChain4j-agentic AgenticScopeJsonSerializationIT.java AgenticScopeSerializer.fromJson deserialization

Published Sep 25, 2026
·
Updated

A flaw has been found in langchain4j up to 1.5.3-beta10/1.11.10-beta18/1.18.1-beta27. This vulnerability affects the function AgenticScopeSerializer.fromJson of the file AgenticScopeJsonSerializationIT.java of the component LangChain4j-agentic. This manipulation causes deserialization. Remote exploitation of the attack is possible. The attack's complexity is rated as high. It is stated that the exploitability is difficult. The exploit has been published and may be used. Upgrading to version 1.5.3-beta11, 1.11.10-beta19 and 1.18.1-beta28 is able to resolve this issue. Upgrading the affected component is advised. The project maintainer kindly explains: "The issue was reported to us privately on 23 July 2026 and fixed in releases published on 29 July 2026. It is tracked as GHSA-gmwr-7wmf-mrjm. Exploitation requires an application to have enabled AgenticScope persistence, which is opt-in, and an attacker who can already write to that store. All maintained release lines have been patched."

Affected Software

1 affected component
maven/dev.langchain4j/langchain4j-agentic<=1.5.3-beta10, <=1.11.10-beta18, <=1.18.1-beta27

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade langchain4j LangChain4j-agentic to a version that resolves this vulnerability.

    Fixed in 1.5.3-beta11
  2. Upgrade

    Upgrade langchain4j LangChain4j-agentic to a version that resolves this vulnerability.

    Fixed in 1.11.10-beta19
  3. Upgrade

    Upgrade langchain4j LangChain4j-agentic to a version that resolves this vulnerability.

    Fixed in 1.18.1-beta28

Event History

Sep 25, 2026
CVE Published
via MITRE·03:15 PM
Data Sourced
via MITRE·03:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeakness
Jan 9, 58706
Event
via NVD·08:21 PM

Frequently Asked Questions

1

Is an application affected if it does not use AgenticScope persistence?

No. Exploitation requires AgenticScope persistence to be enabled, and that feature is opt-in.

2

What access does an attacker need to exploit this issue?

The attacker must already be able to write to the AgenticScope persistence store. Remote exploitation is possible only where that prerequisite is met.

3

Which versions address the issue?

Upgrade to 1.5.3-beta11, 1.11.10-beta19, or 1.18.1-beta28. The maintainer states that all maintained release lines have been patched.

4

What should teams do if they cannot upgrade immediately?

Disable AgenticScope persistence if it is not required, or restrict write access to its persistence store. The described exploitation path depends on both persistence being enabled and attacker-controlled writes to that store.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203