Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-41712 high CVSS 7.5

Vulnerability in org.springframework.ai:spring-ai-client-chat (CVE-2026-41712)

Summary

Vulnerability in org.springframework.ai:spring-ai-client-chat (CVE-2026-41712). Confidential information can be exposed externally. Mitigation: upgrade to 2.0.0-M6 or later.

Original description

The description as published by the source.

Spring AI's chat memory component contained a problematic default that, when not explicitly overridden, could result in unintended data exposure between users.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-41712 has been found in org.springframework.ai:spring-ai-client-chat.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade org.springframework.ai:spring-ai-client-chat to 2.0.0-M6 or later.
If unsure, ask your IT team or search "org.springframework.ai:spring-ai-client-chat CVE-2026-41712" on the vendor's site.

CVE-2026-41712 (org.springframework.ai:spring-ai-client-chat) — CWE-276 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.0.0-M6 — apply immediately
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

A vulnerability (CWE-276) exists in org.springframework.ai:spring-ai-client-chat.

📍 Affected scope

Check the vendor advisory for the affected versions of org.springframework.ai:spring-ai-client-chat.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2.0.0-M6.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

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.

    資産台帳・SBOM・依存マニフェストで org.springframework.ai:spring-ai-client-chat を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.springframework.ai:spring-ai-client-chat to 2.0.0-M6

    ステージング環境で 2.0.0-M6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

maven org.springframework.ai:spring-ai-client-chat
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0-M1"},{"fixed":"2.0.0-M6"}]}]
maven org.springframework.ai:spring-ai-model
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0-M1"},{"fixed":"2.0.0-M6"}]}]
maven org.springframework.ai:spring-ai-advisors-vector-store
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0-M1"},{"fixed":"2.0.0-M6"}]}]

References

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