⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.2

How to Fix CVE-2026-41713: Server-Side Template Injection in Spring AI

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 8.2 - High
Actively exploited?Not currently listed in CISA KEV
Affected1.0.0 < 1.0.7, 1.1.0 < 1.1.6
Fixed inSee vendor advisory
Type (CWE)CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine

What is CVE-2026-41713?

CVE-2026-41713 is a server-side template injection flaw in Spring AI. User input is rendered as part of a template expression, which the engine then evaluates, giving the attacker code execution. Vendor 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.

Why this CVE matters

Server-side template injection is one of the cleanest paths from web request to code execution. The vulnerable parameter is usually attacker-controlled by design, which means proof-of-concept payloads are short and reliable.

For deployments of Spring AI that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

On VMware ESXi, run vmware -vl to read the build number. On vCenter, the version is shown on the login banner and in the admin UI under the Help menu.

How to fix CVE-2026-41713

  1. Read the vendor advisory in full: https://spring.io/security/cve-2026-41713
  2. Upgrade Spring AI to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Update the maven / gradle dependency


# CVE-2026-41713 affects Spring AI 1.0.0 < 1.0.7. Fixed in 1.0.7.
# Vendor advisory: https://spring.io/security/cve-2026-41713

# Maven: bump the dependency in pom.xml then re-resolve.
mvn versions:use-dep-version -Dincludes=spring-ai -DdepVersion=1.0.7 -DforceVersion=true
mvn clean install

# Gradle: bump in build.gradle then refresh.
./gradlew --refresh-dependencies build

# Restart the affected JVM service so the patched JAR loads.
sudo systemctl restart <service-name>

# Verify the runtime is on the patched build.
java -version


# Vendor advisory: https://spring.io/security/cve-2026-41713
# Restart the equivalent Windows service after upgrading the JAR.
Restart-Service -Name "<service-name>"
Get-Service -Name "<service-name>"

Verify the fix landed


# CVE-2026-41713 verification checklist.

# 1. Confirm the running version matches 1.0.7 (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-41713.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://spring.io/security/cve-2026-41713

If you cannot patch immediately

Block the affected endpoint or input from untrusted users. There is no configuration-only mitigation; patch is required.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unexpected administrator accounts in Spring AI, scheduled tasks or cron jobs you did not create, new files in web-accessible directories, and outbound connections to addresses not in your baseline. Suspicious requests to the vulnerable endpoint immediately followed by successful 200-class responses with unusually large bodies are a strong indicator of exploitation.

Frequently asked questions

Is CVE-2026-41713 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-41713?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Spring AI run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*