{
  "@id": "urn:uuid:515fe7f0-ceff-4b4a-b430-a20e6e3efaaf",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 13,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-03T12:06:46.571739+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@2.5.15-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@2.5.15-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T12:06:46.571739+00:00",
      "status_notes": "Vulnerability CVE-2023-20883 does not affect version 2.5.15-tuxcare.1 of org.springframework.boot:spring-boot-autoconfigure. The target Spring Boot 2.5.15 is not affected by CVE-2023-20883. The vulnerability (DoS via proxy caching 404 responses for welcome page requests with non-HTML Accept headers) was fixed in the upstream Spring Boot 2.5.15 release itself. The fix (commit d7ff379fb8 by pwebb@vmware.com) was already present when TuxCare onboarded version 2.5.15, requiring no separate backport. The defense code is fully present: WelcomePageNotAcceptableHandlerMapping returns HTTP 406 (Not Acceptable) instead of falling through to 404, preventing proxy cache pollution.\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 2.5.15 is not affected by CVE-2023-20883. The vulnerability (DoS via proxy caching 404 responses for welcome page requests with non-HTML Accept headers) was fixed in the upstream Spring Boot 2.5.15 release itself. The fix (commit d7ff379fb8 by pwebb@vmware.com) was already present when TuxCare onboarded version 2.5.15, requiring no separate backport. The defense code is fully present: WelcomePageNotAcceptableHandlerMapping returns HTTP 406 (Not Acceptable) instead of falling through to 404, preventing proxy cache pollution.\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@2.5.15-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@2.5.15-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-29T06:49:41.365843+00:00",
      "status_notes": "Vulnerability CVE-2026-40971 does not affect version 2.5.15-tuxcare.1 of org.springframework.boot:spring-boot-autoconfigure. not_affected \u2014 Spring Boot 2.5.15 is not affected by CVE-2026-40971. The vulnerability concerns hostname verification being disabled when using SSL bundles for RabbitMQ connections. However, SSL bundle support for RabbitMQ was not introduced until Spring Boot 3.2.0-RC1 (commit 5556739c8c, October 2023). Version 2.5.15 only supports traditional SSL property-based configuration, which properly applies hostname ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-40971"
      },
      "impact_statement": "not_affected \u2014 Spring Boot 2.5.15 is not affected by CVE-2026-40971. The vulnerability concerns hostname verification being disabled when using SSL bundles for RabbitMQ connections. However, SSL bundle support for RabbitMQ was not introduced until Spring Boot 3.2.0-RC1 (commit 5556739c8c, October 2023). Version 2.5.15 only supports traditional SSL property-based configuration, which properly applies hostname ..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@2.5.15-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@2.5.15-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-40974 affects version 2.5.15-tuxcare.1 of org.springframework.boot:spring-boot-autoconfigure.",
      "vulnerability": {
        "name": "CVE-2026-40974"
      },
      "action_statement": "Vulnerability CVE-2026-40974 affects version 2.5.15-tuxcare.1 of org.springframework.boot:spring-boot-autoconfigure."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@2.5.15-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@2.5.15-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-40992 does not affect version 2.5.15-tuxcare.1 of org.springframework.boot:spring-boot-autoconfigure. not_affected \u2014 Version 2.5.15 is NOT AFFECTED by CVE-2026-40992. The vulnerability requires the automatic SSL configuration feature (Ssl class) introduced in Spring Boot 3.4+. Version 2.5.15 lacks this feature entirely - it has no autoconfiguration code that automatically enables SSL for mail, and therefore no insecure default. All SSL configuration in 2.5.15 must be done manually via spring.mail.properties.*...",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "CVE-2026-40992"
      },
      "impact_statement": "not_affected \u2014 Version 2.5.15 is NOT AFFECTED by CVE-2026-40992. The vulnerability requires the automatic SSL configuration feature (Ssl class) introduced in Spring Boot 3.4+. Version 2.5.15 lacks this feature entirely - it has no autoconfiguration code that automatically enables SSL for mail, and therefore no insecure default. All SSL configuration in 2.5.15 must be done manually via spring.mail.properties.*..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@2.5.15-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.boot/spring-boot-autoconfigure@2.5.15-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-41001 affects version 2.5.15-tuxcare.1 of org.springframework.boot:spring-boot-autoconfigure.",
      "vulnerability": {
        "name": "CVE-2026-41001"
      },
      "action_statement": "Vulnerability CVE-2026-41001 affects version 2.5.15-tuxcare.1 of org.springframework.boot:spring-boot-autoconfigure."
    }
  ]
}