Skip to content
Fencer Intel
high 8.2

CVE-2026-41713 json

Prompt Injection via Memory Poisoning in PromptChatMemoryAdvisor

published 5mo ago modified 14d ago also GHSA-5852-phmh-8fhr , EUVD-2026-29449

cvss
8.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

A malicious user could craft input that is stored in conversation memory and later interpreted by the model in an unintended way. Applications using the affected advisor with user-controlled input may be susceptible to manipulation of model behavior across conversation turns.

Patch / fix

  • maven org.springframework.ai:spring-ai-client-chat 1.0.7, 1.1.6
  • VMware Spring AI 1.0.7, 1.1.6

Is CVE-2026-41713 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
GitHub 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework.ai:spring-ai-client-chat
<1.0.7
>=1.1.0-M1, <1.1.6
1.0.7
1.1.6

Affected products

  • VMware Spring AI

Classification

Weakness
  • CWE-1336 Improper Neutralization of Special Elements Used in a Template Engine

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.