CVE-2026-97869

MEDIUMPre-NVD 4.14.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 4.1 from GitHub Security Advisory (severity: LOW) published 2026-09-25. A secondary CVSS source baseline 4.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-87114 (ENISA EUVD) · GHSA-hg7f-vffm-ppc6 (GitHub Security Advisories)Source: ENISA EUVD

4.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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."

CVSS v3
4.1
EG Score
4.1MEDIUMmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity41% × 45%
Impact severity (EG Severity): CVSS 4.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
15th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.1): severity, escalated by confirmed exploitation. This CVE's 4.1 is its impact severity (EG Severity), not escalated.

EG Severity
4.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 25, 2026

Last Modified

September 28, 2026

Advisory Details (4)

Auto-updated Sep 25, 2026
Patch available. Sources: github_release, github.
Web page

GitHub - langchain4j/langchain4j: LangChain4j is an idiomatic, open-source Java library for building LLM-powered applications on the JVM. It offers a unified API over popular LLM providers and vector stores, and makes implementing tool calling (including MCP support), agents and RAG easy. It integrates seamlessly with enterprise Java frameworks like Quarkus and Spring Boot. · GitHub

https://github.com/langchain4j/langchain4j/
GitHub release Patch Available

1.18.1 and 1.18.1-beta28

Patch available: langchain4j/langchain4j 1.18.1

https://github.com/langchain4j/langchain4j/releases/tag/1.18.1
Web page

CVE/Insecure Jackson Default Typing Leads to Arbitrary Class Instantiation in LangChain4j Agentic Module.md at main · afish3201-debug/CVE · GitHub

https://github.com/afish3201-debug/CVE/blob/main/Insecure%20Jackson%20Default%20Typing%20Leads%20to%20Arbitrary%20Class%20Instantiation%20in%20LangChain4j%20Agentic%20Module.md
GitHub advisoryMentions a patch (unverified)

Unsafe Jackson Default Typing Deserialization in langchain4j-agentic AgenticScopeSerializer · Advisory · langchain4j/langchain4j · GitHub

https://github.com/langchain4j/langchain4j/security/advisories/GHSA-gmwr-7wmf-mrjm

Vendor Advisories for CVE-2026-97869(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 55× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 79 is merged into the row it repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  6. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  7. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  8. 2026-10-25 18:34 UTCEG score recompute
  9. 2026-10-25 18:33 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  10. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  11. 2026-10-25 13:47 UTCEG score recompute
  12. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  19. 2026-10-18 02:56 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  21. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  22. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  23. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  24. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
Show 53 more
  1. 2026-10-12 16:13 UTCEG score recompute
  2. 2026-10-12 16:12 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  3. 2026-10-12 14:39 UTCEG score recompute
  4. 2026-10-11 19:10 UTCEG score recompute
  5. 2026-10-11 16:26 UTCEG score recompute
  6. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  7. 2026-10-11 13:38 UTCEG score recompute
  8. 2026-10-11 06:34 UTCEG score recompute
  9. 2026-10-11 06:34 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-10-10 05:20 UTCEG score recompute
  12. 2026-10-10 05:20 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  13. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-09 04:06 UTCEG score recompute
  15. 2026-10-09 04:06 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  16. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-10-08 02:51 UTCEG score recompute
  18. 2026-10-08 02:51 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-10-07 01:37 UTCEG score recompute
  21. 2026-10-07 01:37 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  22. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  23. 2026-10-06 00:23 UTCEG score recompute
  24. 2026-10-06 00:23 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  25. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  26. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  27. 2026-10-04 23:09 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  28. 2026-10-03 21:55 UTCEG score recompute
  29. 2026-10-03 21:55 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  30. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  31. 2026-10-02 20:38 UTCEG score recompute
  32. 2026-10-02 20:38 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  33. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  34. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  35. 2026-10-01 19:15 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  36. 2026-09-30 18:01 UTCEG score recompute
  37. 2026-09-30 18:01 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  38. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  39. 2026-09-29 16:46 UTCEG score recompute
  40. 2026-09-29 16:46 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  41. 2026-09-28 15:33 UTCEG score recompute
  42. 2026-09-28 15:33 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  43. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  44. 2026-09-27 20:13 UTCEG score recompute
  45. 2026-09-27 20:13 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  46. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  47. 2026-09-26 18:59 UTCEG score recompute
  48. 2026-09-26 18:59 UTCGHSA enrichmentGHSA-hg7f-vffm-ppc6 · GitHub severity LOW · GitHub CVSS 4.1
  49. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  50. 2026-09-25 16:26 UTCEG score recompute
  51. 2026-09-25 16:25 UTCNVD updateCVSS v4 → 1.2
  52. 2026-09-25 15:21 UTCEG score recomputeFirst assessed: 4.1 MEDIUM
  53. 2026-09-25 15:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97869?
CVE-2026-97869 is a medium-severity vulnerability; its CVE record was published on September 25, 2026. 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…
When was the CVE record for CVE-2026-97869 published?
The CVE record for CVE-2026-97869 was published on September 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 28, 2026; the record at its source may have been updated since.
Is CVE-2026-97869 actively exploited?
CVE-2026-97869 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97869?
CVE-2026-97869 has a CVSS base score of 4.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97869?
A fix for CVE-2026-97869 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-97869 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-97869

Explore →

Is Your Infrastructure Affected by CVE-2026-97869?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.