{
  "@id": "urn:uuid:2b2f0fe6-7f36-4118-9288-b8aba2be4a85",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 4,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T04:23:42.223331+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2009-1190 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 CVE-2009-1190 is a vulnerability in JDK versions before 1.6, specifically in the Pattern.compile method's algorithmic complexity handling. Spring Framework 5.3.19 requires JDK 8 or later to run (sourceCompatibility = JavaVersion.VERSION_1_8), making it impossible to deploy this Spring version on the vulnerable JDK versions. The vulnerability cannot manifest because the required runtime environm...",
      "vulnerability": {
        "name": "CVE-2009-1190"
      },
      "impact_statement": "not_affected \u2014 CVE-2009-1190 is a vulnerability in JDK versions before 1.6, specifically in the Pattern.compile method's algorithmic complexity handling. Spring Framework 5.3.19 requires JDK 8 or later to run (sourceCompatibility = JavaVersion.VERSION_1_8), making it impossible to deploy this Spring version on the vulnerable JDK versions. The vulnerability cannot manifest because the required runtime environm..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-06T17:34:37.123717+00:00",
      "status_notes": "Vulnerability CVE-2011-2730 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. Prechecker: The upstream fix is already in this version's source history (commits 62ccc8dd, 9772eb84, b8d86330). Version 5.3.19 is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-wv88-pf73-x22p (affected up to 3.0.6), NVD (affected up to 3.0.5), Snyk (affected up to 3.0.6).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2730"
      },
      "impact_statement": "Prechecker: The upstream fix is already in this version's source history (commits 62ccc8dd, 9772eb84, b8d86330). Version 5.3.19 is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-wv88-pf73-x22p (affected up to 3.0.6), NVD (affected up to 3.0.5), Snyk (affected up to 3.0.6)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 Spring Framework 5.3.19 is NOT vulnerable to CVE-2011-2894. The vulnerability affected versions 3.0.0 through 3.0.5 and was fixed in version 3.0.6 (2011) by adding an acceptProxyClasses configuration flag that blocks deserialization of proxy classes. The target repository (version 5.3.19, released 2022) already contains this upstream fix as part of its codebase - the fix was present in the upst...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 5.3.19 is NOT vulnerable to CVE-2011-2894. The vulnerability affected versions 3.0.0 through 3.0.5 and was fixed in version 3.0.6 (2011) by adding an acceptProxyClasses configuration flag that blocks deserialization of proxy classes. The target repository (version 5.3.19, released 2022) already contains this upstream fix as part of its codebase - the fix was present in the upst..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2014-3578 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 CVE-2014-3578 directory traversal vulnerability is NOT present in Spring Framework 5.3.19. The fix for SPR-11793 (preventing colon-based path prefix confusion) was introduced in Spring 4.1.0.RC1 (May 2014) and has been part of the upstream codebase ever since. The target version 5.3.19 (released 2022) already contains this fix from upstream, not as a TuxCare backport.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-3578"
      },
      "impact_statement": "not_affected \u2014 CVE-2014-3578 directory traversal vulnerability is NOT present in Spring Framework 5.3.19. The fix for SPR-11793 (preventing colon-based path prefix confusion) was introduced in Spring 4.1.0.RC1 (May 2014) and has been part of the upstream codebase ever since. The target version 5.3.19 (released 2022) already contains this fix from upstream, not as a TuxCare backport."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2015-0201 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5 due to predictable session IDs in the SockJS client. The vulnerability was caused by using AlternativeJdkIdGenerator (which uses SecureRandom only for the initial seed, then Random thereafter). The fix switched to JdkIdGenerator (which calls UUID.randomUUID() using SecureRandom). This fix was implemented by the upstream Spring Framework ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-0201"
      },
      "impact_statement": "not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5 due to predictable session IDs in the SockJS client. The vulnerability was caused by using AlternativeJdkIdGenerator (which uses SecureRandom only for the initial seed, then Random thereafter). The fix switched to JdkIdGenerator (which calls UUID.randomUUID() using SecureRandom). This fix was implemented by the upstream Spring Framework ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2015-5211 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. Spring Framework 5.3.19 is not affected by CVE-2015-5211 (RFD attack). The upstream fix (commit 2bd1daa75e, October 2015) was already present in the 5.3.19 release (April 2022). Furthermore, the codebase has evolved beyond the original fix with multiple additional protections: JSONP support was completely removed (June 2018), path extension content negotiation is disabled by default (favorPathExtension=false), and a comprehensive safe extension whitelist with automatic Content-Disposition header injection prevents any malicious file downloads.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.2.0, < 4.2.2; >= 4.0.0, < 4.1.8; < 3.2.15), NVD (= 3.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.0; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.2.0; = 4.2.1), Snyk (>= 3.2.0.RELEASE, < 3.2.15.RELEASE; >= 4.0.0.RELEASE, < 4.1.8.RELEASE; >= 4.2.0.RELEASE, < 4.2.2.RELEASE; <= 0; <= 0).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-5211"
      },
      "impact_statement": "Spring Framework 5.3.19 is not affected by CVE-2015-5211 (RFD attack). The upstream fix (commit 2bd1daa75e, October 2015) was already present in the 5.3.19 release (April 2022). Furthermore, the codebase has evolved beyond the original fix with multiple additional protections: JSONP support was completely removed (June 2018), path extension content negotiation is disabled by default (favorPathExtension=false), and a comprehensive safe extension whitelist with automatic Content-Disposition header injection prevents any malicious file downloads.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.2.0, < 4.2.2; >= 4.0.0, < 4.1.8; < 3.2.15), NVD (= 3.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.0; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.2.0; = 4.2.1), Snyk (>= 3.2.0.RELEASE, < 3.2.15.RELEASE; >= 4.0.0.RELEASE, < 4.1.8.RELEASE; >= 4.2.0.RELEASE, < 4.2.2.RELEASE; <= 0; <= 0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. Spring Framework 5.3.19 is not affected by CVE-2016-5007. The vulnerability (pattern matching inconsistency between Spring Security and Spring MVC that could allow authorization bypass) was fixed in upstream Spring Framework v4.3.1.RELEASE (April 2016) through the introduction of the HandlerMappingIntrospector API and MatchableHandlerMapping interface (commit a30ab30e4e). This fix has been present in all Spring Framework versions since 4.3.1, including 5.3.19. The fix provides an SPI that allows Spring Security to query Spring MVC's handler mappings using the exact same pattern matching logic, eliminating the inconsistency that caused the vulnerability. The fix was authored by upstream Spring developers (Rossen Stoyanchev at Pivotal) and shipped in the upstream release that 5.3.19 is based on, not applied by TuxCare.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.1), NVD (= 3.2.0; = 4.0.0; = 4.1.0; = 4.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 3.2.15; = 3.2.16; = 3.2.17; = 3.2.18; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.1.8; = 4.1.9; = 4.2.1; = 4.2.2; = 4.2.3; = 4.2.4; = 4.2.5; = 4.2.6; = 4.2.7; = 4.2.8; = 4.2.9), cve.org (>= 3.2, < 3.3; >= 4.0, < 4.1; >= 4.1, < 4.2; >= 4.2, < 4.3; < 3.2), Snyk (>= 3.2.0.RELEASE, < 4.3.1.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-5007"
      },
      "impact_statement": "Spring Framework 5.3.19 is not affected by CVE-2016-5007. The vulnerability (pattern matching inconsistency between Spring Security and Spring MVC that could allow authorization bypass) was fixed in upstream Spring Framework v4.3.1.RELEASE (April 2016) through the introduction of the HandlerMappingIntrospector API and MatchableHandlerMapping interface (commit a30ab30e4e). This fix has been present in all Spring Framework versions since 4.3.1, including 5.3.19. The fix provides an SPI that allows Spring Security to query Spring MVC's handler mappings using the exact same pattern matching logic, eliminating the inconsistency that caused the vulnerability. The fix was authored by upstream Spring developers (Rossen Stoyanchev at Pivotal) and shipped in the upstream release that 5.3.19 is based on, not applied by TuxCare.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.1), NVD (= 3.2.0; = 4.0.0; = 4.1.0; = 4.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 3.2.15; = 3.2.16; = 3.2.17; = 3.2.18; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.1.8; = 4.1.9; = 4.2.1; = 4.2.2; = 4.2.3; = 4.2.4; = 4.2.5; = 4.2.6; = 4.2.7; = 4.2.8; = 4.2.9), cve.org (>= 3.2, < 3.3; >= 4.0, < 4.1; >= 4.1, < 4.2; >= 4.2, < 4.3; < 3.2), Snyk (>= 3.2.0.RELEASE, < 4.3.1.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2018-11040 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. CVE-2018-11040 does not affect Spring Framework 5.3.19. The vulnerable JSONP functionality has been completely removed from the codebase in an upstream commit (ac37b678) dated June 7, 2018, which predates the first TuxCare commit. The target contains no JSONP code - no jsonpParameterNames field, no AbstractJsonpResponseBodyAdvice class, and no JSONP-related methods. The vulnerability pattern cannot manifest because the code that processes JSONP query parameters does not exist.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE), NVD (< 4.3.18; >= 5.0.0, < 5.0.7), cve.org (>= 5.0.x, < 5.0.7; >= 4.3.x, < 4.3.18), Snyk (>= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-11040"
      },
      "impact_statement": "CVE-2018-11040 does not affect Spring Framework 5.3.19. The vulnerable JSONP functionality has been completely removed from the codebase in an upstream commit (ac37b678) dated June 7, 2018, which predates the first TuxCare commit. The target contains no JSONP code - no jsonpParameterNames field, no AbstractJsonpResponseBodyAdvice class, and no JSONP-related methods. The vulnerability pattern cannot manifest because the code that processes JSONP query parameters does not exist.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE), NVD (< 4.3.18; >= 5.0.0, < 5.0.7), cve.org (>= 5.0.x, < 5.0.7; >= 4.3.x, < 4.3.18), Snyk (>= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1199 (path parameter bypass vulnerability) is NOT present in Spring Framework 5.3.19. The upstream security fixes for SPR-16616, SPR-16526, and SPR-16296 were already included in the Spring Framework 5.3.19 release that TuxCare onboarded. The defense code that normalizes path separators, removes duplicate slashes, and validates encoded paths to prevent traversal attacks is fully presen...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1199 (path parameter bypass vulnerability) is NOT present in Spring Framework 5.3.19. The upstream security fixes for SPR-16616, SPR-16526, and SPR-16296 were already included in the Spring Framework 5.3.19 release that TuxCare onboarded. The defense code that normalizes path separators, removes duplicate slashes, and validates encoded paths to prevent traversal attacks is fully presen..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2018-1257 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 The target (Spring Framework 5.3.19) is not affected by CVE-2018-1257. The fix for this ReDoS vulnerability was already present in the upstream v5.3.19 release that TuxCare onboarded. The fix commit ff2228fdaf from April 2018 added the ability to disable selector header support by setting selectorHeaderName to null, which guards against malicious SpEL expressions. The current code has the prote...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1257"
      },
      "impact_statement": "not_affected \u2014 The target (Spring Framework 5.3.19) is not affected by CVE-2018-1257. The fix for this ReDoS vulnerability was already present in the upstream v5.3.19 release that TuxCare onboarded. The fix commit ff2228fdaf from April 2018 added the ability to disable selector header support by setting selectorHeaderName to null, which guards against malicious SpEL expressions. The current code has the prote..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2018-1258 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. CVE-2018-1258 authorization bypass vulnerability is NOT present in Spring Framework 5.3.19. The vulnerable method resolution pattern was fixed by upstream vendor (Juergen Hoeller @ Spring/Pivotal) in commits aa11721ff0 (SPR-16757) and eaff2c28a78 (SPR-16779) on 2018-04-27, both shipped in upstream releases v5.1.0 and v5.3.0 respectively, before TuxCare onboarded version 5.3.19. The fixes ensure proper target method resolution for proxy classes, preventing annotation lookup failures that could bypass Spring Security method-level authorization.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.5.RELEASE, < 5.0.6.RELEASE), NVD (= 5.0.5), cve.org (= 5.0.5), Snyk (>= 5.0.5.RELEASE, < 5.0.6.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1258"
      },
      "impact_statement": "CVE-2018-1258 authorization bypass vulnerability is NOT present in Spring Framework 5.3.19. The vulnerable method resolution pattern was fixed by upstream vendor (Juergen Hoeller @ Spring/Pivotal) in commits aa11721ff0 (SPR-16757) and eaff2c28a78 (SPR-16779) on 2018-04-27, both shipped in upstream releases v5.1.0 and v5.3.0 respectively, before TuxCare onboarded version 5.3.19. The fixes ensure proper target method resolution for proxy classes, preventing annotation lookup failures that could bypass Spring Security method-level authorization.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.5.RELEASE, < 5.0.6.RELEASE), NVD (= 5.0.5), cve.org (= 5.0.5), Snyk (>= 5.0.5.RELEASE, < 5.0.6.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2018-1271 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1271 (directory traversal via URL-encoded path sequences in Spring static resource serving) is NOT present in target version 5.3.19. The upstream fix commits (91b803a231, 0e28bee0f1) were authored by Spring Framework maintainers and shipped in the upstream release before TuxCare onboarding. Both servlet (spring-webmvc) and reactive (spring-webflux) resource handlers contain the complet...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1271"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1271 (directory traversal via URL-encoded path sequences in Spring static resource serving) is NOT present in target version 5.3.19. The upstream fix commits (91b803a231, 0e28bee0f1) were authored by Spring Framework maintainers and shipped in the upstream release before TuxCare onboarding. Both servlet (spring-webmvc) and reactive (spring-webflux) resource handlers contain the complet..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2018-1272 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. CVE-2018-1272 affects Spring Framework versions 5.0 prior to 5.0.5 and 4.3 prior to 4.3.15. The vulnerability involves predictable multipart boundary generation using java.util.Random instead of SecureRandom, allowing attackers to predict boundaries and inject malicious multipart content. The target repository at version 5.3.19 already contains the upstream fix (commit ab2410c754 by rstoyanchev@pivotal.io) that was included in Spring Framework 5.0.5.RELEASE in March 2018. The current code uses SecureRandom for cryptographically unpredictable boundary generation, making the attack infeasible. This fix was part of the upstream v5.3.19 release that TuxCare onboarded, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.15; >= 5.0.0, < 5.0.5), NVD (>= 4.3.0, < 4.3.15; >= 5.0, < 5.0.5), cve.org (< 5.0.5; < 4.3.15), Snyk (>= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; >= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; <= 0).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1272"
      },
      "impact_statement": "CVE-2018-1272 affects Spring Framework versions 5.0 prior to 5.0.5 and 4.3 prior to 4.3.15. The vulnerability involves predictable multipart boundary generation using java.util.Random instead of SecureRandom, allowing attackers to predict boundaries and inject malicious multipart content. The target repository at version 5.3.19 already contains the upstream fix (commit ab2410c754 by rstoyanchev@pivotal.io) that was included in Spring Framework 5.0.5.RELEASE in March 2018. The current code uses SecureRandom for cryptographically unpredictable boundary generation, making the attack infeasible. This fix was part of the upstream v5.3.19 release that TuxCare onboarded, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.15; >= 5.0.0, < 5.0.5), NVD (>= 4.3.0, < 4.3.15; >= 5.0, < 5.0.5), cve.org (< 5.0.5; < 4.3.15), Snyk (>= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; >= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; <= 0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2018-15756 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. CVE-2018-15756 fix for HTTP range DoS attack is already present in Spring Framework 5.3.19. The vulnerability allowed attackers to send Range headers with excessive ranges (>100) or overlapping ranges to cause resource exhaustion. The upstream fix (MAX_RANGES=100 limit and sum validation) was implemented in October 2018 and included in all 5.3.x releases from 5.3.0 onwards (October 2020). The target version 5.3.19-tuxcare.3 is based on upstream v5.3.19 which naturally includes this fix. No TuxCare-specific backport was needed.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.1.0.RELEASE, < 5.1.1.RELEASE; >= 5.0.0.RELEASE, < 5.0.10.RELEASE; >= 4.2.0.RELEASE, < 4.3.20.RELEASE), NVD (>= 4.2.0, < 4.3.20; >= 5.0.0, < 5.0.10; = 5.1.0), cve.org (= 5.1; >= 5.0.0, <= 5.0.9; >= 4.3, <= 4.3.19), Snyk (>= 4.2.0.RELEASE, < 4.3.20.RELEASE; >= 5.0.0.RELEASE, < 5.0.10.RELEASE; >= 5.1.0.RELEASE, < 5.1.1.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-15756"
      },
      "impact_statement": "CVE-2018-15756 fix for HTTP range DoS attack is already present in Spring Framework 5.3.19. The vulnerability allowed attackers to send Range headers with excessive ranges (>100) or overlapping ranges to cause resource exhaustion. The upstream fix (MAX_RANGES=100 limit and sum validation) was implemented in October 2018 and included in all 5.3.x releases from 5.3.0 onwards (October 2020). The target version 5.3.19-tuxcare.3 is based on upstream v5.3.19 which naturally includes this fix. No TuxCare-specific backport was needed.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.1.0.RELEASE, < 5.1.1.RELEASE; >= 5.0.0.RELEASE, < 5.0.10.RELEASE; >= 4.2.0.RELEASE, < 4.3.20.RELEASE), NVD (>= 4.2.0, < 4.3.20; >= 5.0.0, < 5.0.10; = 5.1.0), cve.org (= 5.1; >= 5.0.0, <= 5.0.9; >= 4.3, <= 4.3.19), Snyk (>= 4.2.0.RELEASE, < 4.3.20.RELEASE; >= 5.0.0.RELEASE, < 5.0.10.RELEASE; >= 5.1.0.RELEASE, < 5.1.1.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2021-22060 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 Spring Framework 5.3.19 is NOT affected by CVE-2021-22060. The vulnerability affects versions 5.3.0-5.3.13, but the fix was included in upstream version 5.3.14 (December 2021) and is present in 5.3.19 (April 2022). The fix commits (99c7608ffe and e9083d7d20) were authored by upstream Spring Framework developers and shipped in the upstream release before TuxCare onboarded this version. LogFormat...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22060"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 5.3.19 is NOT affected by CVE-2021-22060. The vulnerability affects versions 5.3.0-5.3.13, but the fix was included in upstream version 5.3.14 (December 2021) and is present in 5.3.19 (April 2022). The fix commits (99c7608ffe and e9083d7d20) were authored by upstream Spring Framework developers and shipped in the upstream release before TuxCare onboarded this version. LogFormat..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2021-22096 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 Spring Framework 5.3.19 is NOT affected by CVE-2021-22096 (log injection vulnerability). The fix for this vulnerability was already included in the upstream Spring Framework 5.3.19 release (released April 13, 2022). The upstream patches by Rossen Stoyanchev (VMware) added sanitization of newlines and control characters in LogFormatUtils (commit 99c7608f, Dec 8, 2021) and applied this sanitizati...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22096"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 5.3.19 is NOT affected by CVE-2021-22096 (log injection vulnerability). The fix for this vulnerability was already included in the upstream Spring Framework 5.3.19 release (released April 13, 2022). The upstream patches by Rossen Stoyanchev (VMware) added sanitization of newlines and control characters in LogFormatUtils (commit 99c7608f, Dec 8, 2021) and applied this sanitizati..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-10T04:23:42.223331+00:00",
      "status_notes": "Vulnerability CVE-2024-22233 does not affect version 5.3.19-tuxcare.4 of org.springframework:spring-core. Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version is not affected because the vulnerable cached request-URI regex matching mechanism is absent. In spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:184, getMatchableHandlerMapping wraps the request and resolves its handler mapping without consulting a cached result. The class contains no CachedResult, cache filter, or request-URI-as-regex comparison.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-22233"
      },
      "impact_statement": "Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version is not affected because the vulnerable cached request-URI regex matching mechanism is absent. In spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:184, getMatchableHandlerMapping wraps the request and resolves its handler mapping without consulting a cached result. The class contains no CachedResult, cache filter, or request-URI-as-regex comparison."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2025-41249 is fixed in version 5.3.19-tuxcare.4 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2025-41249"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.19-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-05T13:16:57.573968+00:00",
      "status_notes": "Vulnerability CVE-2026-41848 is fixed in version 5.3.19-tuxcare.4 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2026-41848"
      }
    }
  ]
}