{
  "@id": "urn:uuid:2c7db105-d8a3-4519-b7f7-debbcec8247c",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 45,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-06T17:40:04.386984+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T12:53:36.275404+00:00",
      "status_notes": "Vulnerability CVE-2009-1190 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2009-1190 is a JDK vulnerability in Pattern.compile (JDK before 1.6) that causes CPU exhaustion when compiling regex patterns with multiple optional groups. While Spring Framework 5.3.9 contains serializable classes with Pattern fields (e.g., UriTemplate) that compile user-provided regex without validation, the target is not affected because it requires Java 8+ (JDK 1.8+), and the underlyin...",
      "vulnerability": {
        "name": "CVE-2009-1190"
      },
      "impact_statement": "not_affected \u2014 CVE-2009-1190 is a JDK vulnerability in Pattern.compile (JDK before 1.6) that causes CPU exhaustion when compiling regex patterns with multiple optional groups. While Spring Framework 5.3.9 contains serializable classes with Pattern fields (e.g., UriTemplate) that compile user-provided regex without validation, the target is not affected because it requires Java 8+ (JDK 1.8+), and the underlyin..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-06T17:40:04.386984+00:00",
      "status_notes": "Vulnerability CVE-2011-2730 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. Prechecker: No vulnerable code from the fix was found, and the functions the fix changes were not found in this version. Version 5.3.9 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: No vulnerable code from the fix was found, and the functions the fix changes were not found in this version. Version 5.3.9 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.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T09:54:00.051000+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2011-2894 does not affect Spring Framework 5.3.9. The upstream vendor (Spring/VMware) applied the fix in commit 7d8aa05c40 (July 2011), which added an acceptProxyClasses flag to control proxy deserialization. This defense mechanism was included in the upstream 5.3.9 release that TuxCare onboarded. The defense defaults to permissive (acceptProxyClasses=true) for backward compatibility but ca...",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 CVE-2011-2894 does not affect Spring Framework 5.3.9. The upstream vendor (Spring/VMware) applied the fix in commit 7d8aa05c40 (July 2011), which added an acceptProxyClasses flag to control proxy deserialization. This defense mechanism was included in the upstream 5.3.9 release that TuxCare onboarded. The defense defaults to permissive (acceptProxyClasses=true) for backward compatibility but ca..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-02T17:10:00.096270+00:00",
      "status_notes": "Vulnerability CVE-2014-3578 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2014-3578 is a directory traversal vulnerability in Spring Framework 3.x before 3.2.9 and 4.0 before 4.0.5. The target repository is Spring Framework 5.3.9-tuxcare.4. The vulnerability has been fixed in the upstream release: the StringUtils.cleanPath method contains the security fix (lines 684-686) that checks if a prefix contains a forward slash and rejects it to prevent path traversal att...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-3578"
      },
      "impact_statement": "not_affected \u2014 CVE-2014-3578 is a directory traversal vulnerability in Spring Framework 3.x before 3.2.9 and 4.0 before 4.0.5. The target repository is Spring Framework 5.3.9-tuxcare.4. The vulnerability has been fixed in the upstream release: the StringUtils.cleanPath method contains the security fix (lines 684-686) that checks if a prefix contains a forward slash and rejects it to prevent path traversal att..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T19:20:43.319935+00:00",
      "status_notes": "Vulnerability CVE-2015-0201 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5, where the Java SockJS client generated predictable session IDs using AlternativeJdkIdGenerator (which uses java.util.Random after an initial SecureRandom seed). The target version 5.3.9 uses JdkIdGenerator, which calls UUID.randomUUID() for cryptographically secure session ID generation. The fix (commit 52b8f34468, Jan 2015) was authore...",
      "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, where the Java SockJS client generated predictable session IDs using AlternativeJdkIdGenerator (which uses java.util.Random after an initial SecureRandom seed). The target version 5.3.9 uses JdkIdGenerator, which calls UUID.randomUUID() for cryptographically secure session ID generation. The fix (commit 52b8f34468, Jan 2015) was authore..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:08:56.260651+00:00",
      "status_notes": "Vulnerability CVE-2015-5211 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. Spring Framework 5.3.9 is not affected by CVE-2015-5211 (Reflected File Download attack). The vulnerability required two components: (1) JSONP callback functionality that could inject attacker-controlled content into responses, and (2) improper file extension extraction from URLs. Both vulnerabilities were eliminated in upstream Spring Framework before 5.3.9 was released. JSONP support was completely removed in Spring 5.0 (June 2018, commit ac37b678a3), and the file extension extraction logic was refactored in July 2016 (commit adc595b5f1) to use UriUtils.extractFileExtension() which properly handles query parameters (?), fragments (#), and path parameters (;) - effectively including the CVE-2015-5211 fix. The TuxCare onboarding of 5.3.9 (commit b3968c443f) inherited these upstream protections.\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.9 is not affected by CVE-2015-5211 (Reflected File Download attack). The vulnerability required two components: (1) JSONP callback functionality that could inject attacker-controlled content into responses, and (2) improper file extension extraction from URLs. Both vulnerabilities were eliminated in upstream Spring Framework before 5.3.9 was released. JSONP support was completely removed in Spring 5.0 (June 2018, commit ac37b678a3), and the file extension extraction logic was refactored in July 2016 (commit adc595b5f1) to use UriUtils.extractFileExtension() which properly handles query parameters (?), fragments (#), and path parameters (;) - effectively including the CVE-2015-5211 fix. The TuxCare onboarding of 5.3.9 (commit b3968c443f) inherited these upstream protections.\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.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:18:44.496921+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. Spring Framework 5.3.9 is not affected by CVE-2016-5007. The fix (commit a30ab30e4e) was authored by the upstream vendor (Pivotal) and shipped in the upstream 5.3.9 release that TuxCare onboarded. The target contains all fix components: MatchableHandlerMapping interface, HandlerMappingIntrospector helper class, and RequestMatchResult. Both AbstractUrlHandlerMapping and RequestMappingHandlerMapping implement MatchableHandlerMapping with match() methods that provide consistent pattern matching semantics aligned with Spring MVC's internal routing logic, preventing the authorization bypass vulnerability.\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.9 is not affected by CVE-2016-5007. The fix (commit a30ab30e4e) was authored by the upstream vendor (Pivotal) and shipped in the upstream 5.3.9 release that TuxCare onboarded. The target contains all fix components: MatchableHandlerMapping interface, HandlerMappingIntrospector helper class, and RequestMatchResult. Both AbstractUrlHandlerMapping and RequestMappingHandlerMapping implement MatchableHandlerMapping with match() methods that provide consistent pattern matching semantics aligned with Spring MVC's internal routing logic, preventing the authorization bypass vulnerability.\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.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T14:00:42.857553+00:00",
      "status_notes": "Vulnerability CVE-2018-11040 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. Spring Framework 5.3.9 is NOT AFFECTED by CVE-2018-11040. The vulnerability concerned automatic JSONP support being enabled by default via the jsonpParameterNames field in MappingJackson2JsonView and AbstractJsonpResponseBodyAdvice class. In version 5.3.9, all JSONP support has been completely removed (not just disabled) by upstream Spring Framework commit ac37b678a3, which was already part of the upstream 5.3.9 release that TuxCare onboarded. No vulnerable code patterns exist in the target.\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": "Spring Framework 5.3.9 is NOT AFFECTED by CVE-2018-11040. The vulnerability concerned automatic JSONP support being enabled by default via the jsonpParameterNames field in MappingJackson2JsonView and AbstractJsonpResponseBodyAdvice class. In version 5.3.9, all JSONP support has been completely removed (not just disabled) by upstream Spring Framework commit ac37b678a3, which was already part of the upstream 5.3.9 release that TuxCare onboarded. No vulnerable code patterns exist in the target.\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.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T01:15:16.880365+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 Spring Framework 5.3.9 is not affected by CVE-2018-1199. The vulnerability, which allowed bypassing security constraints via URL-encoded path traversal (using duplicate slashes, backslashes, or percent-encoded directory traversal sequences like %2E%2E%2F), was fixed in upstream versions 4.3.14 and 5.0.3 in March 2018. Version 5.3.9 (released July 2021) already contains all necessary defenses: p...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 5.3.9 is not affected by CVE-2018-1199. The vulnerability, which allowed bypassing security constraints via URL-encoded path traversal (using duplicate slashes, backslashes, or percent-encoded directory traversal sequences like %2E%2E%2F), was fixed in upstream versions 4.3.14 and 5.0.3 in March 2018. Version 5.3.9 (released July 2021) already contains all necessary defenses: p..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T10:20:00.109102+00:00",
      "status_notes": "Vulnerability CVE-2018-1257 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1257 affects Spring Framework versions 5.0.x prior to 5.0.6 and 4.3.x prior to 4.3.17. The target repository is Spring Framework 5.3.9, released in July 2021, years after the vulnerability was disclosed (April 2018) and fixed (May 2018). The fix that allows disabling the selector header feature to prevent ReDoS attacks was already present in the upstream 5.3.9 release when TuxCare onbo...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1257"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1257 affects Spring Framework versions 5.0.x prior to 5.0.6 and 4.3.x prior to 4.3.17. The target repository is Spring Framework 5.3.9, released in July 2021, years after the vulnerability was disclosed (April 2018) and fixed (May 2018). The fix that allows disabling the selector header feature to prevent ReDoS attacks was already present in the upstream 5.3.9 release when TuxCare onbo..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2018-1258 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. CVE-2018-1258 is NOT present in Spring Framework 5.3.9-tuxcare.4. The vulnerability affected version 5.0.5 and was fixed upstream in April 2018 by Juergen Hoeller (Pivotal). All required fixes are present in the target: AopUtils.getMostSpecificMethod() no longer excludes proxy classes (line 196), AnnotationMethodMatcher includes proxy class check (line 77), and CacheAspectSupport/ApplicationListenerMethodAdapter properly resolve target methods. The fixes were already included in the upstream 5.3.9 release that TuxCare onboarded in September 2026.\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 is NOT present in Spring Framework 5.3.9-tuxcare.4. The vulnerability affected version 5.0.5 and was fixed upstream in April 2018 by Juergen Hoeller (Pivotal). All required fixes are present in the target: AopUtils.getMostSpecificMethod() no longer excludes proxy classes (line 196), AnnotationMethodMatcher includes proxy class check (line 77), and CacheAspectSupport/ApplicationListenerMethodAdapter properly resolve target methods. The fixes were already included in the upstream 5.3.9 release that TuxCare onboarded in September 2026.\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.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T19:04:00.117091+00:00",
      "status_notes": "Vulnerability CVE-2018-1271 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1271 directory traversal vulnerability is NOT present in Spring Framework 5.3.9. The upstream vendor (Pivotal/VMware) fixed this vulnerability in Spring Framework 5.0.5 and 4.3.15 (March 2018). The target version 5.3.9 (released July 2020, over 2 years after the fix) already contains all the security patches. The fix commits (SPR-16616) are present in HEAD and were part of the upstream...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1271"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1271 directory traversal vulnerability is NOT present in Spring Framework 5.3.9. The upstream vendor (Pivotal/VMware) fixed this vulnerability in Spring Framework 5.0.5 and 4.3.15 (March 2018). The target version 5.3.9 (released July 2020, over 2 years after the fix) already contains all the security patches. The fix commits (SPR-16616) are present in HEAD and were part of the upstream..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T12:30:34.591989+00:00",
      "status_notes": "Vulnerability CVE-2018-1272 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. CVE-2018-1272 affects Spring Framework versions < 5.0.5 and 4.3 < 4.3.15, where predictable Random was used for multipart boundary generation, allowing attackers to inject extra parts and achieve privilege escalation. The target version 5.3.9 already contains the upstream fix (commit ab2410c754) that replaced Random with SecureRandom, making boundaries cryptographically unpredictable. This fix was shipped in the upstream 5.3.9 release before TuxCare onboarded it (first TuxCare commit b3968c443f is \"Onboard version 5.3.9\"). The vulnerable pattern is not present in the target.\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.5 and 4.3 < 4.3.15, where predictable Random was used for multipart boundary generation, allowing attackers to inject extra parts and achieve privilege escalation. The target version 5.3.9 already contains the upstream fix (commit ab2410c754) that replaced Random with SecureRandom, making boundaries cryptographically unpredictable. This fix was shipped in the upstream 5.3.9 release before TuxCare onboarded it (first TuxCare commit b3968c443f is \"Onboard version 5.3.9\"). The vulnerable pattern is not present in the target.\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.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:44:14.640121+00:00",
      "status_notes": "Vulnerability CVE-2018-15756 does not affect version 5.3.9-tuxcare.2 of org.springframework:spring-core. CVE-2018-15756 is not present in Spring Framework 5.3.9. The vulnerability allows DoS attacks via malicious HTTP Range headers with excessive range counts or overlapping ranges. The upstream fix (commit 423aa28ed5 by rstoyanchev@pivotal.io, Oct 2018) was already included in the Spring Framework 5.3.9 release that TuxCare onboarded. Both required defenses are present in the target code: (1) MAX_RANGES=100 limit enforced at line 136-138, and (2) sum-of-ranges validation at lines 185-195. The vulnerable pattern was removed by the upstream vendor before TuxCare's work on this version began.\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 is not present in Spring Framework 5.3.9. The vulnerability allows DoS attacks via malicious HTTP Range headers with excessive range counts or overlapping ranges. The upstream fix (commit 423aa28ed5 by rstoyanchev@pivotal.io, Oct 2018) was already included in the Spring Framework 5.3.9 release that TuxCare onboarded. Both required defenses are present in the target code: (1) MAX_RANGES=100 limit enforced at line 136-138, and (2) sum-of-ranges validation at lines 185-195. The vulnerable pattern was removed by the upstream vendor before TuxCare's work on this version began.\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": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-21T16:44:27.378062+00:00",
      "status_notes": "Vulnerability CVE-2021-22060 affects version 5.3.9-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2021-22060"
      },
      "action_statement": "Vulnerability CVE-2021-22060 affects version 5.3.9-tuxcare.2 of org.springframework:spring-core."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-21T16:44:27.378062+00:00",
      "status_notes": "Vulnerability CVE-2021-22096 affects version 5.3.9-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2021-22096"
      },
      "action_statement": "Vulnerability CVE-2021-22096 affects version 5.3.9-tuxcare.2 of org.springframework:spring-core."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-29T03:39:22.988337+00:00",
      "status_notes": "Vulnerability CVE-2024-22233 affects version 5.3.9-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2024-22233"
      },
      "action_statement": "Vulnerability CVE-2024-22233 affects version 5.3.9-tuxcare.2 of org.springframework:spring-core."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-21T16:44:27.378062+00:00",
      "status_notes": "Vulnerability CVE-2025-41249 affects version 5.3.9-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2025-41249"
      },
      "action_statement": "Vulnerability CVE-2025-41249 affects version 5.3.9-tuxcare.2 of org.springframework:spring-core."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.9-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-21T16:44:27.378062+00:00",
      "status_notes": "Vulnerability CVE-2026-41848 is fixed in version 5.3.9-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2026-41848"
      }
    }
  ]
}