Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-41713: A malicious user could craft input that is stored in conversation memory and later interpreted by the model in

37
Routine
HIGH 8.2REMOTEUPGRADE

CVE-2026-41713 is a high-severity flaw (CVSS 8.2) affecting spring ai. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score8.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.2% (top 88%)
CISA exploited listNo
WeaknessCWE-1336
Published2026-05-12
Last modified2026-10-26
Publisher (CNA): VMware · Vendor: vmware

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vmware spring ai UPGRADE
Affected: >= 1.0.0 and < 1.0.7 · >= 1.1.0 and < 1.1.6
Fixed in: 1.0.7, 1.1.6
Safe to downgrade to: a release before 1.0.0
1. Check installed version
apt-cache policy spring-ai || rpm -q spring-ai || spring-ai --version
2. UPGRADE to 1.0.7 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade spring-ai
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade spring-ai
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)
apt-cache madison spring-ai sudo apt install spring-ai=<VERSION_BEFORE_1.0.0> sudo apt-mark hold spring-ai
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spring-ai sudo dnf downgrade spring-ai-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add spring-ai
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41713?

spring ai: upgrade to 1.0.7, 1.1.6. Exact commands for each OS are on this page.

Is CVE-2026-41713 being exploited?

CVE-2026-41713 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41713 affect?

CVE-2026-41713 affects spring ai. Severity is high (CVSS 8.2). 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

How urgent is CVE-2026-41713?

Priority 37/100. High severity; Remotely exploitable, no login, no user action

Software pages

VMware vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.