{
  "@id": "urn:uuid:a375416e-4685-4d56-9de0-d2fa85e51819",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 4,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-03T11:40:17.696488+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.ai/spring-ai-client-chat@1.0.9-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.ai/spring-ai-client-chat@1.0.9-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T11:40:17.696488+00:00",
      "status_notes": "Vulnerability CVE-2026-41712 does not affect version 1.0.9-tuxcare.1 of org.springframework.ai:spring-ai-client-chat. Target version 1.0.9 is not affected by CVE-2026-41712. The vulnerability (DEFAULT_CONVERSATION_ID allowing chat memory sharing across users) was fixed in the upstream Spring AI release. The affected versions are 1.0.0-1.0.6 and 1.1.0-1.1.5; version 1.0.9 contains the fix commit e1402dea5 authored by upstream (christian.tzolov@broadcom.com) that removes the problematic default conversation ID and mandates explicit per-user conversation IDs, preventing data exposure between users.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.0.7; >= 1.1.0-M1, < 1.1.6; >= 2.0.0-M1, < 2.0.0-M6; < 1.0.7; >= 1.1.0-M1, < 1.1.6; >= 2.0.0-M1, < 2.0.0-M6; < 1.0.7; >= 1.1.0-M1, < 1.1.6; >= 2.0.0-M1, < 2.0.0-M6), NVD (>= 1.0.0, < 1.0.7; >= 1.1.0, < 1.1.6), cve.org (>= 1.0.0, < 1.0.7; >= 1.1.0, < 1.1.6), Snyk (< 1.0.7; >= 1.1.0-M1, < 1.1.6; <= 0).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-41712"
      },
      "impact_statement": "Target version 1.0.9 is not affected by CVE-2026-41712. The vulnerability (DEFAULT_CONVERSATION_ID allowing chat memory sharing across users) was fixed in the upstream Spring AI release. The affected versions are 1.0.0-1.0.6 and 1.1.0-1.1.5; version 1.0.9 contains the fix commit e1402dea5 authored by upstream (christian.tzolov@broadcom.com) that removes the problematic default conversation ID and mandates explicit per-user conversation IDs, preventing data exposure between users.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.0.7; >= 1.1.0-M1, < 1.1.6; >= 2.0.0-M1, < 2.0.0-M6; < 1.0.7; >= 1.1.0-M1, < 1.1.6; >= 2.0.0-M1, < 2.0.0-M6; < 1.0.7; >= 1.1.0-M1, < 1.1.6; >= 2.0.0-M1, < 2.0.0-M6), NVD (>= 1.0.0, < 1.0.7; >= 1.1.0, < 1.1.6), cve.org (>= 1.0.0, < 1.0.7; >= 1.1.0, < 1.1.6), Snyk (< 1.0.7; >= 1.1.0-M1, < 1.1.6; <= 0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.ai/spring-ai-client-chat@1.0.9-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.ai/spring-ai-client-chat@1.0.9-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T11:40:17.696488+00:00",
      "status_notes": "Vulnerability CVE-2026-41713 does not affect version 1.0.9-tuxcare.1 of org.springframework.ai:spring-ai-client-chat. The target Spring AI 1.0.9 is NOT AFFECTED by CVE-2026-41713 (prompt injection via conversation memory). The vulnerable pattern (plain-text memory interpolation without escaping) is not present. The upstream vendor (Broadcom) shipped the fix in the 1.0.9 release before TuxCare onboarding. All three memory advisor implementations are protected: PromptChatMemoryAdvisor and VectorStoreChatMemoryAdvisor XML-escape user-controlled memory content and wrap it in typed elements before system prompt interpolation; MessageChatMemoryAdvisor passes memory as typed Message objects, avoiding system prompt serialization entirely.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.0.7; >= 1.1.0-M1, < 1.1.6), NVD (>= 1.0.0, < 1.0.7; >= 1.1.0, < 1.1.6), cve.org (>= 1.0.0, < 1.0.7; >= 1.1.0, < 1.1.6), Snyk (< 1.0.7; >= 1.1.0-M1, < 1.1.6; < 1.0.7; >= 1.1.0-M1, < 1.1.6; < 1.0.7; >= 1.1.0-M1, < 1.1.6; < 1.0.7; >= 1.1.0-M1, < 1.1.6).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-41713"
      },
      "impact_statement": "The target Spring AI 1.0.9 is NOT AFFECTED by CVE-2026-41713 (prompt injection via conversation memory). The vulnerable pattern (plain-text memory interpolation without escaping) is not present. The upstream vendor (Broadcom) shipped the fix in the 1.0.9 release before TuxCare onboarding. All three memory advisor implementations are protected: PromptChatMemoryAdvisor and VectorStoreChatMemoryAdvisor XML-escape user-controlled memory content and wrap it in typed elements before system prompt interpolation; MessageChatMemoryAdvisor passes memory as typed Message objects, avoiding system prompt serialization entirely.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.0.7; >= 1.1.0-M1, < 1.1.6), NVD (>= 1.0.0, < 1.0.7; >= 1.1.0, < 1.1.6), cve.org (>= 1.0.0, < 1.0.7; >= 1.1.0, < 1.1.6), Snyk (< 1.0.7; >= 1.1.0-M1, < 1.1.6; < 1.0.7; >= 1.1.0-M1, < 1.1.6; < 1.0.7; >= 1.1.0-M1, < 1.1.6; < 1.0.7; >= 1.1.0-M1, < 1.1.6)."
    }
  ]
}