{
  "@id": "urn:uuid:efb40010-4af6-4ea7-813a-686233217923",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 2,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-03T11:40:52.629939+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.ai/spring-ai-mariadb-store@1.1.8-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.ai/spring-ai-mariadb-store@1.1.8-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T11:40:52.629939+00:00",
      "status_notes": "Vulnerability CVE-2026-22730 does not affect version 1.1.8-tuxcare.1 of org.springframework.ai:spring-ai-mariadb-store. The target repository (Spring AI 1.1.8) is NOT vulnerable to CVE-2026-22730. The SQL injection vulnerability in MariaDBFilterExpressionConverter was fixed by the upstream vendor (commit 5b6723811 by ilayaperumal.gopinathan@broadcom.com) and this fix was already present in the upstream release 1.1.8 that TuxCare onboarded. The vulnerable pattern (unescaped SQL string concatenation) is not present in the target; it has been replaced with proper SQL escaping via the emitSqlString method that prevents injection attacks by escaping single quotes, backslashes, control characters, and Unicode control characters.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 1.1.0-M1, < 1.1.3; < 1.0.4), NVD (>= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3), cve.org (>= 1.0.x, < 1.0.4; >= 1.1.x, < 1.1.3), Snyk (>= 1.0.0-M5, < 1.0.4; >= 1.1.0-M1, < 1.1.3; >= 2.0.0-M1, < 2.0.0-M3).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-22730"
      },
      "impact_statement": "The target repository (Spring AI 1.1.8) is NOT vulnerable to CVE-2026-22730. The SQL injection vulnerability in MariaDBFilterExpressionConverter was fixed by the upstream vendor (commit 5b6723811 by ilayaperumal.gopinathan@broadcom.com) and this fix was already present in the upstream release 1.1.8 that TuxCare onboarded. The vulnerable pattern (unescaped SQL string concatenation) is not present in the target; it has been replaced with proper SQL escaping via the emitSqlString method that prevents injection attacks by escaping single quotes, backslashes, control characters, and Unicode control characters.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 1.1.0-M1, < 1.1.3; < 1.0.4), NVD (>= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3), cve.org (>= 1.0.x, < 1.0.4; >= 1.1.x, < 1.1.3), Snyk (>= 1.0.0-M5, < 1.0.4; >= 1.1.0-M1, < 1.1.3; >= 2.0.0-M1, < 2.0.0-M3)."
    }
  ]
}