How severe is CVE-2026-41705?

CVE-2026-41705 has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-41705?

CVE-2026-41705 affects the following packages: org.springframework.ai:spring-ai-milvus-store (Maven), org.springframework.ai:spring-ai-milvus-store (Maven), org.springframework.ai:spring-ai-typesense-store (Maven), org.springframework.ai:spring-ai-typesense-store (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-41705?

Update org.springframework.ai:spring-ai-milvus-store to 1.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41705 is resolved across your whole dependency graph.

How do I detect CVE-2026-41705 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.ai:spring-ai-milvus-store. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2026-41705 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-41705?

O3 pinpoints whether CVE-2026-41705 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2026-41705 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-41705 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2026-41705?

CVE-2026-41705 is classified as Expression Language Injection (CWE-917). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-41705 published, and has it been updated?

CVE-2026-41705 was published on May 9, 2026 and was last updated on July 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2026-41705

HIGH

CVE-2026-41705 is a high-severity (CVSS 8.6) Expression Language Injection vulnerability in org.springframework.ai:spring-ai-milvus-store. O3 Security confirms whether CVE-2026-41705 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Spring AI's MilvusVectorStore#doDelete(List) implementation is vulnerable to filter-expression injection via unsanitized document IDs

Also known asGHSA-v632-2m87-7469

Published

May 9, 2026

Updated

Jul 27, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Jul 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected

☕org.springframework.ai:spring-ai-milvus-store☕org.springframework.ai:spring-ai-milvus-store☕org.springframework.ai:spring-ai-typesense-store☕org.springframework.ai:spring-ai-typesense-store

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Spring AI's MilvusVectorStore#doDelete(List) implementation is vulnerable to filter-expression injection via unsanitized document IDs. Spring AI 1.0.x: affected from 1.0.0 through latest 1.0.x; upgrade to 1.0.7 or greater. Spring AI 1.1.x: affected from 1.1.0 through latest 1.1.x; upgrade to 1.1.6 or greater.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.ai:spring-ai-milvus-store`	≥ 1.0.0&&< 1.0.7	1.0.7
☕Maven	`org.springframework.ai:spring-ai-milvus-store`	≥ 1.1.0&&< 1.1.6	1.1.6
☕Maven	`org.springframework.ai:spring-ai-typesense-store`	≥ 1.0.0&&< 1.0.7	1.0.7
☕Maven	`org.springframework.ai:spring-ai-typesense-store`	≥ 1.1.0&&< 1.1.6	1.1.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.ai:spring-ai-milvus-store. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework.ai:spring-ai-milvus-store to 1.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41705 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-41705 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-41705. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-41705 in your dependencies?

O3 detects CVE-2026-41705 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works