AI / ML
CVE-2026-47835 high CVSS 8.6

Vulnerability in CVE-2026-47835 (CVE-2026-47835)

Summary

vulnerability in CVE-2026-47835 (CVE-2026-47835). Confidential information can be exposed externally.

Original description

The description as published by the source.

In Spring AI Vector Stores, special characters could be used to force the execution of arbitrary queries in Elasticsearch, OpenSearch, and GemFire VectorDB. Affected components: spring-ai-elasticsearch-store, spring-ai-opensearch-store, spring-ai-gemfire-store.

Affected versions:
Spring AI 1.0.0 through 1.0.x (fix 1.0.9).
Spring AI 1.1.0 through 1.1.x (fix 1.1.8).

Source: NIST National Vulnerability Database NVD GitHub Advisory

AI summary

Written by an external AI model and may contain mistakes. Check the original description and references below before acting on it.

A vulnerability tracked as CVE-2026-47835 has been found in CVE-2026-47835.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-47835 CVE-2026-47835" on the vendor's site.

CVE-2026-47835 (CVE-2026-47835) — CWE-943 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Spring AI Vector Storesにおける特別な文字による任意のクエリ実行の脆弱性。

📍 Affected scope

spring-ai-elasticsearch-store、spring-ai-opensearch-store、spring-ai-gemfire-store。

🔥 Severity

脆弱性はCVSSスコア8.6の高リスクとされ、攻撃者が任意のクエリを実行できる可能性があるため。

🔧 How to fix

バージョン1.0.9または1.1.8へアップデートする。

🛡️ Workaround

情報なし

🔍 Detection

パッチ未適用の影響範囲を確認するために、バージョンを確認する。

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    依存マニフェストで影響コンポーネントを特定する。

  2. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.springframework.ai:spring-ai-opensearch-store
[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.0"},{"fixed":"1.1.8"}]}]
maven org.springframework.ai:spring-ai-elasticsearch-store
[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.0"},{"fixed":"1.1.8"}]}]
maven org.springframework.ai:spring-ai-gemfire-store
[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.0"},{"fixed":"1.1.8"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details