CVE-2026-22738
A public proof of concept exists; no exploitation attested.
- Published2026-03-27
- Fixed in1.1.4 · 1.0.5
- WeaknessCWE-88 · CWE-917
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In Spring AI, a SpEL injection vulnerability exists in SimpleVectorStore when a user-supplied value is used as a filter expression key. A malicious actor could exploit this to execute arbitrary code. Only applications that use SimpleVectorStore and pass user-supplied input as a filter expression key are affected. This issue affects Spring AI: from 1.0.0 before 1.0.5, from 1.1.0 before 1.1.4.
Timeline
dates in UTC- 2026-03-2706:16CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-22738?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-22738?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.1 | ≥ 1.1.0, < 1.1.4 | 1.1.4 | NVD |
| 1.1 | ≥ 1.1.0-M1, < 1.1.4 | 1.1.4 | OSV |
| 1.0 | ≥ 1.0.0, < 1.0.5 | 1.0.5 | NVD · OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Vmware spring ai to 1.1.4 · 1.0.5
Advisories and patches
- spring.ioVendor Advisory
Detection
read 2026-10-23 19:25 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 2 repositories, unverifiedn0n4m3x41/CVE-2026-22738-POCrockmelodies/CVE-2026-22738 PoC-in-GitHub
Sources
- CISA-ADPSSVC decisionnone2026-03-28
- OpenCVESSVC decisionnone—
- CNACVSS 3.19.8read 2026-10-23
- CISA-ADPweakness (CWE)CWE-882026-03-27
- NVDweakness (CWE)CWE-917read 2026-10-23
- FIRST EPSSEPSS score1.1 %2026-10-22
- PoC-in-GitHubproof of concept2read 2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-03-27
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2026-22738?
Is CVE-2026-22738 actively exploited?
What is the CVSS score for CVE-2026-22738?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.