# CVE-2026-41713: Prompt Injection via Memory Poisoning in PromptChatMemoryAdvisor

> Attackers can manipulate AI model behavior via prompt injection in Spring AI's memory advisor, requiring library upgrades.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-5852-phmh-8fhr, MINI-3ff7-m467-fmmg, MINI-8rr9-h8jr-6jc2

## What is CVE-2026-41713?

CVE-2026-41713 is a high-severity vulnerability in VMware Spring AI, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2026-41713?

4 open source packages ship an affected version, including org.springframework.ai:spring-ai-client-chat. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.ai:spring-ai-client-chat` | Maven | All versions | 1.0.7 |
| `org.springframework.ai:spring-ai-client-chat` | Maven | All versions | 1.0.7 |
| `org.springframework.ai:spring-ai-client-chat` | Maven | From 1.1.0-M1 | 1.1.6 |
| `org.springframework.ai:spring-ai-client-chat` | Maven | From 1.1.0-M1 | 1.1.6 |

Products: Vmware Spring Ai.

## How do I fix CVE-2026-41713?

Upgrade org.springframework.ai:spring-ai-client-chat to a fixed version for your release line: 1.0.7 or 1.1.6.

## Is CVE-2026-41713 being exploited?

There is no known exploitation of CVE-2026-41713 in the wild and no public exploit code.

## Other vulnerabilities in VMware Spring AI

- [CVE-2026-22738](https://insights.sbomify.com/CVE-2026-22738/): SpEL Injection via Unescaped Filter Key in SimpleVectorStore Leads to Remote Code Execution (critical 9.8)
- [CVE-2026-40978](https://insights.sbomify.com/CVE-2026-40978/): Spring AI has SQL Injection in CosmosDBVectorStore.doDelete() (high 8.8)
- [CVE-2026-22730](https://insights.sbomify.com/CVE-2026-22730/): CVE-2026-22730: SQL Injection in Spring AI MariaDBFilterExpressionConverter (high 8.8)
- [CVE-2026-47835](https://insights.sbomify.com/CVE-2026-47835/): Spring AI vector store metadata filtering to handle special characters in Elasticsearch, OpenSearch, and GemFire Vector Stores (high 8.6)
- [CVE-2026-41705](https://insights.sbomify.com/CVE-2026-41705/): Spring AI's MilvusVectorStore#doDelete(List) implementation is vulnerable to filter-expression injection via unsanitized document IDs (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41713 and fix it if it is affected.

What it is: CVE-2026-41713 is a high-severity vulnerability in VMware Spring AI, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41713 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.ai:spring-ai-client-chat (Maven): affected all versions; fixed in 1.0.7
- org.springframework.ai:spring-ai-client-chat (Maven): affected all versions; fixed in 1.0.7
- org.springframework.ai:spring-ai-client-chat (Maven): affected from 1.1.0-M1; fixed in 1.1.6
- org.springframework.ai:spring-ai-client-chat (Maven): affected from 1.1.0-M1; fixed in 1.1.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41713/ (Markdown: https://insights.sbomify.com/CVE-2026-41713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41713
- OSV: https://osv.dev/vulnerability/CVE-2026-41713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41713/
Summaries are generated and may contain mistakes; the official description above is the record.