Categories
CVE-2026-41713 high CVSS 8.2

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

Summary

Vulnerability in org.springframework.ai:spring-ai-client-chat (CVE-2026-41713). Data can be tampered with by attackers. Mitigation: upgrade to 1.1.6 or later.

Original description

The description as published by the source.

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.

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-41713 has been found in org.springframework.ai:spring-ai-client-chat.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: upgrade org.springframework.ai:spring-ai-client-chat to 1.1.6 or later.
If unsure, ask your IT team or search "org.springframework.ai:spring-ai-client-chat CVE-2026-41713" on the vendor's site.

CVE-2026-41713 (org.springframework.ai:spring-ai-client-chat) — CWE-1336 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.1.6 — 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-1336) 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 8.2/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.1.6.

🛡️ 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 1.1.6

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

  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":"1.1.0-M1"},{"fixed":"1.1.6"}]}]

References

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