{
  "@id": "urn:uuid:85f03071-54b9-415e-8978-e23a64e2a4f8",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 13,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-03T12:04:03.421384+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@3.3.13-tuxcare.13",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@3.3.13-tuxcare.13"
          }
        }
      ],
      "timestamp": "2026-11-03T12:04:03.421384+00:00",
      "status_notes": "Vulnerability CVE-2023-20883 does not affect version 3.3.13-tuxcare.13 of org.springframework.boot:spring-boot-autoconfigure. The target Spring Boot 3.3.13-tuxcare.18 is NOT AFFECTED by CVE-2023-20883. The upstream fix (commit 418dd1ba5b authored by pwebb@vmware.com) was already present in the upstream Spring Boot 3.3.13 release before TuxCare onboarded it. The fix prevents DoS attacks via reverse proxy cache pollution by returning HTTP 406 (NOT_ACCEPTABLE) instead of 404 when requests to \"/\" have Accept headers that don't match text/html. Both required handler mappings (WelcomePageHandlerMapping and WelcomePageNotAcceptableHandlerMapping) are present and properly registered in WebMvcAutoConfiguration.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 3.0.0, < 3.0.7; >= 2.7.0, < 2.7.12; >= 2.6.0, < 2.6.15; < 2.5.15), NVD (< 2.5.14; >= 2.6.0, <= 2.6.14; >= 2.7.0, <= 2.7.11; >= 3.0.0, <= 3.0.6), cve.org (>= 3.0.0, <= 3.0.6; >= 2.7.0, <= 2.7.11; >= 2.6.0, <= 2.6.14; >= 2.5.0, <= 2.5.14), Snyk (< 2.5.15; >= 2.6.0, < 2.6.15; >= 2.7.0, < 2.7.12; >= 3.0.0, < 3.0.7).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-20883"
      },
      "impact_statement": "The target Spring Boot 3.3.13-tuxcare.18 is NOT AFFECTED by CVE-2023-20883. The upstream fix (commit 418dd1ba5b authored by pwebb@vmware.com) was already present in the upstream Spring Boot 3.3.13 release before TuxCare onboarded it. The fix prevents DoS attacks via reverse proxy cache pollution by returning HTTP 406 (NOT_ACCEPTABLE) instead of 404 when requests to \"/\" have Accept headers that don't match text/html. Both required handler mappings (WelcomePageHandlerMapping and WelcomePageNotAcceptableHandlerMapping) are present and properly registered in WebMvcAutoConfiguration.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 3.0.0, < 3.0.7; >= 2.7.0, < 2.7.12; >= 2.6.0, < 2.6.15; < 2.5.15), NVD (< 2.5.14; >= 2.6.0, <= 2.6.14; >= 2.7.0, <= 2.7.11; >= 3.0.0, <= 3.0.6), cve.org (>= 3.0.0, <= 3.0.6; >= 2.7.0, <= 2.7.11; >= 2.6.0, <= 2.6.14; >= 2.5.0, <= 2.5.14), Snyk (< 2.5.15; >= 2.6.0, < 2.6.15; >= 2.7.0, < 2.7.12; >= 3.0.0, < 3.0.7)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@3.3.13-tuxcare.13",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@3.3.13-tuxcare.13"
          }
        }
      ],
      "timestamp": "2026-10-29T06:46:50.295018+00:00",
      "status_notes": "Vulnerability CVE-2026-40971 does not affect version 3.3.13-tuxcare.13 of org.springframework.boot:spring-boot-autoconfigure. not_affected \u2014 Spring Boot 3.3.13-tuxcare.18 is NOT AFFECTED by CVE-2026-40971. The vulnerability exists only in Spring Boot 3.5.x+ which introduced the `connectionDetails.getSslBundle()` API (commit e26ccbe028). The target uses the older property-based `ssl.getBundle()` API which correctly applies hostname verification for both SSL bundle and non-bundle configurations. The vulnerable code pattern (skipping s...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-40971"
      },
      "impact_statement": "not_affected \u2014 Spring Boot 3.3.13-tuxcare.18 is NOT AFFECTED by CVE-2026-40971. The vulnerability exists only in Spring Boot 3.5.x+ which introduced the `connectionDetails.getSslBundle()` API (commit e26ccbe028). The target uses the older property-based `ssl.getBundle()` API which correctly applies hostname verification for both SSL bundle and non-bundle configurations. The vulnerable code pattern (skipping s..."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@3.3.13-tuxcare.13",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@3.3.13-tuxcare.13"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-40974 is fixed in version 3.3.13-tuxcare.13 of org.springframework.boot:spring-boot-autoconfigure.",
      "vulnerability": {
        "name": "CVE-2026-40974"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@3.3.13-tuxcare.13",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@3.3.13-tuxcare.13"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-40992 does not affect version 3.3.13-tuxcare.13 of org.springframework.boot:spring-boot-autoconfigure. CVE-2026-40992 affects only Spring Boot >= 3.4.0 (ranges 3.4.0-3.4.16, 3.5.0-3.5.14, 4.0.0-4.0.6 per spring.io/security/cve-2026-40992). The vulnerable code path is the mail SSL auto-configuration (spring.mail.ssl.*), which sets an SSL socket factory without mail.<proto>.ssl.checkserveridentity. That feature was introduced in Spring Boot 3.4.0. 3.3.13 predates it: MailProperties has no Ssl class and the mail autoconfigure package has zero SSL/socketFactory/checkserveridentity references.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-40992"
      },
      "impact_statement": "CVE-2026-40992 affects only Spring Boot >= 3.4.0 (ranges 3.4.0-3.4.16, 3.5.0-3.5.14, 4.0.0-4.0.6 per spring.io/security/cve-2026-40992). The vulnerable code path is the mail SSL auto-configuration (spring.mail.ssl.*), which sets an SSL socket factory without mail.<proto>.ssl.checkserveridentity. That feature was introduced in Spring Boot 3.4.0. 3.3.13 predates it: MailProperties has no Ssl class and the mail autoconfigure package has zero SSL/socketFactory/checkserveridentity references."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@3.3.13-tuxcare.13",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@3.3.13-tuxcare.13"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-41001 is fixed in version 3.3.13-tuxcare.13 of org.springframework.boot:spring-boot-autoconfigure.",
      "vulnerability": {
        "name": "CVE-2026-41001"
      }
    }
  ]
}