{
  "@id": "urn:uuid:0ae34c5f-ed50-429d-9b2d-4abaed03110d",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 52,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-06T17:33:27.361958+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T12:25:00.536736+00:00",
      "status_notes": "Vulnerability CVE-2009-1190 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.1.4 is not affected by CVE-2009-1190. The vulnerability required Java object deserialization from untrusted remote sources to trigger catastrophic backtracking in JDK <1.6's Pattern.compile. Spring Framework 6.1.4 does not expose Java object deserialization via HTTP endpoints (uses JSON/XML/Protobuf instead), has no RMI or remoting features (removed in Spring 5.3+), and only ...",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "CVE-2009-1190"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.1.4 is not affected by CVE-2009-1190. The vulnerability required Java object deserialization from untrusted remote sources to trigger catastrophic backtracking in JDK <1.6's Pattern.compile. Spring Framework 6.1.4 does not expose Java object deserialization via HTTP endpoints (uses JSON/XML/Protobuf instead), has no RMI or remoting features (removed in Spring 5.3+), and only ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-06T17:33:27.361958+00:00",
      "status_notes": "Vulnerability CVE-2011-2730 does not affect version 6.1.4-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 6.1.4 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 6.1.4 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@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T09:41:00.106715+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2011-2894 affects Spring Framework 3.0.0-3.0.5 via unsafe proxy class deserialization in RMI remoting. The target (Spring Framework 6.1.4) is not affected because: (1) the acceptProxyClasses protection was added to ConfigurableObjectInputStream in upstream commit 7d8aa05c40 (July 2011) and shipped in the upstream release before TuxCare onboarded this version, and (2) the vulnerable RMI remo...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 CVE-2011-2894 affects Spring Framework 3.0.0-3.0.5 via unsafe proxy class deserialization in RMI remoting. The target (Spring Framework 6.1.4) is not affected because: (1) the acceptProxyClasses protection was added to ConfigurableObjectInputStream in upstream commit 7d8aa05c40 (July 2011) and shipped in the upstream release before TuxCare onboarded this version, and (2) the vulnerable RMI remo..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-02T16:42:00.216861+00:00",
      "status_notes": "Vulnerability CVE-2014-3578 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.1.4 is not affected by CVE-2014-3578. The directory traversal vulnerability (allowing arbitrary file access via crafted URLs with colons in non-protocol positions) was fixed in upstream Spring Framework in May 2014 by commit 8ee46510385. This fix was already present in the upstream 6.1.4 release (2024) that TuxCare onboarded. The vulnerable code pattern does not exist in this...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-3578"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.1.4 is not affected by CVE-2014-3578. The directory traversal vulnerability (allowing arbitrary file access via crafted URLs with colons in non-protocol positions) was fixed in upstream Spring Framework in May 2014 by commit 8ee46510385. This fix was already present in the upstream 6.1.4 release (2024) that TuxCare onboarded. The vulnerable code pattern does not exist in this..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T19:12:11.834364+00:00",
      "status_notes": "Vulnerability CVE-2015-0201 does not affect version 6.1.4-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 used SecureRandom only for initial seed, then non-cryptographic Random thereafter). The target version 6.1.4 already contains the upstream fix from Spring Framework 4.1.5+ that switched to JdkIdGenerator using UUID.randomUUID() for crypt...",
      "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 used SecureRandom only for initial seed, then non-cryptographic Random thereafter). The target version 6.1.4 already contains the upstream fix from Spring Framework 4.1.5+ that switched to JdkIdGenerator using UUID.randomUUID() for crypt..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:01:12.948527+00:00",
      "status_notes": "Vulnerability CVE-2015-5211 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. The target Spring Framework 6.1.4 is NOT affected by CVE-2015-5211 (Reflected File Download vulnerability). The upstream fix authored by Rossen Stoyanchev (rstoyanchev@pivotal.io) in commit 2bd1daa75e was already present in the Spring Framework 6.1.4 release before TuxCare onboarded this version. The defense mechanism adds Content-Disposition headers with safe filenames for responses with non-whitelisted file extensions, preventing RFD exploits. The vulnerable pattern (missing Content-Disposition protection) is not present in the target.\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": "The target Spring Framework 6.1.4 is NOT affected by CVE-2015-5211 (Reflected File Download vulnerability). The upstream fix authored by Rossen Stoyanchev (rstoyanchev@pivotal.io) in commit 2bd1daa75e was already present in the Spring Framework 6.1.4 release before TuxCare onboarded this version. The defense mechanism adds Content-Disposition headers with safe filenames for responses with non-whitelisted file extensions, preventing RFD exploits. The vulnerable pattern (missing Content-Disposition protection) is not present in the target.\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@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:13:59.149107+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. CVE-2016-5007 addresses authorization bypass due to pattern matching inconsistencies between Spring Security and Spring MVC. The upstream vendor (Pivotal/Spring) fixed this in April 2016 by introducing the HandlerMappingIntrospector API (commit a30ab30e4e9ae021fdda04e9abfc228476b846b5). This fix was already present in Spring Framework 6.1.4 when TuxCare onboarded it in August 2026. The target repository contains all defense components: MatchableHandlerMapping interface, HandlerMappingIntrospector class, RequestMatchResult class, and implementations in AbstractUrlHandlerMapping and RequestMappingHandlerMapping. The vulnerable pattern (inconsistent pattern matching between security and MVC layers) is not present in version 6.1.4.\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": "CVE-2016-5007 addresses authorization bypass due to pattern matching inconsistencies between Spring Security and Spring MVC. The upstream vendor (Pivotal/Spring) fixed this in April 2016 by introducing the HandlerMappingIntrospector API (commit a30ab30e4e9ae021fdda04e9abfc228476b846b5). This fix was already present in Spring Framework 6.1.4 when TuxCare onboarded it in August 2026. The target repository contains all defense components: MatchableHandlerMapping interface, HandlerMappingIntrospector class, RequestMatchResult class, and implementations in AbstractUrlHandlerMapping and RequestMappingHandlerMapping. The vulnerable pattern (inconsistent pattern matching between security and MVC layers) is not present in version 6.1.4.\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@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:55:21.996343+00:00",
      "status_notes": "Vulnerability CVE-2018-11040 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. CVE-2018-11040 affects Spring Framework versions with automatic JSONP enablement through default parameter names \"jsonp\" and \"callback\" in MappingJackson2JsonView. The target version 6.1.4-tuxcare.8 is not affected because JSONP support was completely removed from Spring Framework 5.1 onwards. Upstream commit ac37b678a3 (June 2018) deleted all JSONP code including the vulnerable jsonpParameterNames field, AbstractJsonpResponseBodyAdvice class, and JSONP transport handlers. This removal was part of the upstream 6.1.4 release before TuxCare onboarding.\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 affects Spring Framework versions with automatic JSONP enablement through default parameter names \"jsonp\" and \"callback\" in MappingJackson2JsonView. The target version 6.1.4-tuxcare.8 is not affected because JSONP support was completely removed from Spring Framework 5.1 onwards. Upstream commit ac37b678a3 (June 2018) deleted all JSONP code including the vulnerable jsonpParameterNames field, AbstractJsonpResponseBodyAdvice class, and JSONP transport handlers. This removal was part of the upstream 6.1.4 release before TuxCare onboarding.\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@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T01:03:00.096337+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 The target Spring Framework 6.1.4-tuxcare.9 is not affected by CVE-2018-1199. The vulnerability fix (SPR-16616) was already present in the upstream Spring Framework 6.1.4 release that TuxCare onboarded. The fix includes path normalization (backslash-to-slash conversion, duplicate slash removal) and URL-decoded path validation to prevent security constraint bypasses via path parameters with spec...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 The target Spring Framework 6.1.4-tuxcare.9 is not affected by CVE-2018-1199. The vulnerability fix (SPR-16616) was already present in the upstream Spring Framework 6.1.4 release that TuxCare onboarded. The fix includes path normalization (backslash-to-slash conversion, duplicate slash removal) and URL-decoded path validation to prevent security constraint bypasses via path parameters with spec..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T09:10:31.335583+00:00",
      "status_notes": "Vulnerability CVE-2018-1257 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.1.4 is not affected by CVE-2018-1257. The vulnerability (DoS via malicious STOMP selector header causing regex/expression parsing exhaustion) was fixed in upstream Spring Framework 4.3.17 and 5.0.6 (April 2018). The fix - a null-check that skips selector expression parsing when the feature is disabled - is present in version 6.1.4. Additionally, as of Spring Framework 6.1, th...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1257"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.1.4 is not affected by CVE-2018-1257. The vulnerability (DoS via malicious STOMP selector header causing regex/expression parsing exhaustion) was fixed in upstream Spring Framework 4.3.17 and 5.0.6 (April 2018). The fix - a null-check that skips selector expression parsing when the feature is disabled - is present in version 6.1.4. Additionally, as of Spring Framework 6.1, th..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2018-1258 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. CVE-2018-1258 describes an authorization bypass in Spring Framework 5.0.5 when using method security with Spring Security. The vulnerability stems from incorrect method resolution for dynamic proxy classes, causing security annotations on target implementations to be missed during expression evaluation. The target repository (Spring Framework 6.1.4-tuxcare.9) is NOT AFFECTED because the upstream vendor fixes (commits eaff2c28a7 and aa11721ff0 by Juergen Hoeller, April 2018) were already present in the Spring Framework 6.1.4 release that TuxCare onboarded. The vulnerable code pattern (improper proxy class handling in AopUtils.getMostSpecificMethod and cache/event expression evaluators) has been removed by the upstream fixes.\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 describes an authorization bypass in Spring Framework 5.0.5 when using method security with Spring Security. The vulnerability stems from incorrect method resolution for dynamic proxy classes, causing security annotations on target implementations to be missed during expression evaluation. The target repository (Spring Framework 6.1.4-tuxcare.9) is NOT AFFECTED because the upstream vendor fixes (commits eaff2c28a7 and aa11721ff0 by Juergen Hoeller, April 2018) were already present in the Spring Framework 6.1.4 release that TuxCare onboarded. The vulnerable code pattern (improper proxy class handling in AopUtils.getMostSpecificMethod and cache/event expression evaluators) has been removed by the upstream fixes.\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@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T18:42:00.223368+00:00",
      "status_notes": "Vulnerability CVE-2018-1271 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.1.4 is not affected by CVE-2018-1271. The directory traversal vulnerability via URL-encoded backslash sequences was fixed in upstream Spring Framework prior to 6.1.4 (CVE affects versions 5.0 prior to 5.0.5 and 4.3 prior to 4.3.15). The fix was already present in the upstream 6.1.4 release that TuxCare onboarded. Both PathResourceResolver and ResourceHttpRequestHandler contai...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1271"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.1.4 is not affected by CVE-2018-1271. The directory traversal vulnerability via URL-encoded backslash sequences was fixed in upstream Spring Framework prior to 6.1.4 (CVE affects versions 5.0 prior to 5.0.5 and 4.3 prior to 4.3.15). The fix was already present in the upstream 6.1.4 release that TuxCare onboarded. Both PathResourceResolver and ResourceHttpRequestHandler contai..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T12:23:26.744347+00:00",
      "status_notes": "Vulnerability CVE-2018-1272 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. Spring Framework 6.1.4 is NOT affected by CVE-2018-1272. The target already uses SecureRandom (not the vulnerable Random) for multipart boundary generation. This fix was shipped in the upstream Spring Framework 6.1.4 release (commit ab2410c754 by rstoyanchev@pivotal.io) before TuxCare onboarded the version. The vulnerable code 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": "Spring Framework 6.1.4 is NOT affected by CVE-2018-1272. The target already uses SecureRandom (not the vulnerable Random) for multipart boundary generation. This fix was shipped in the upstream Spring Framework 6.1.4 release (commit ab2410c754 by rstoyanchev@pivotal.io) before TuxCare onboarded the version. The vulnerable code 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@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:36:59.528750+00:00",
      "status_notes": "Vulnerability CVE-2018-15756 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. The target Spring Framework 6.1.4 is not affected by CVE-2018-15756. The vulnerability's fix (range count limit and overlap validation) was already included in the upstream Spring Framework 6.1.4 release when TuxCare onboarded it. The CVE affects versions 5.1, 5.0.x prior to 5.0.10, and 4.3.x prior to 4.3.20 - version 6.1.4 is significantly newer and includes the security protections by default. Both required defenses are present: MAX_RANGES=100 limit in parseRanges() at line 137-139, and sum-of-ranges validation in toResourceRegions() at lines 186-196.\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": "The target Spring Framework 6.1.4 is not affected by CVE-2018-15756. The vulnerability's fix (range count limit and overlap validation) was already included in the upstream Spring Framework 6.1.4 release when TuxCare onboarded it. The CVE affects versions 5.1, 5.0.x prior to 5.0.10, and 4.3.x prior to 4.3.20 - version 6.1.4 is significantly newer and includes the security protections by default. Both required defenses are present: MAX_RANGES=100 limit in parseRanges() at line 137-139, and sum-of-ranges validation in toResourceRegions() at lines 186-196.\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@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-31T20:28:08.192368+00:00",
      "status_notes": "Vulnerability CVE-2021-22060 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2021-22060 affects Spring Framework versions 5.3.0-5.3.13, 5.2.0-5.2.18, and older. The target version 6.1.4 is significantly newer and already contains the upstream vendor's fix (commit 99c7608ffe \"Replace both EOL and control characters\" by Rossen Stoyanchev @vmware.com). The fix was shipped in the upstream Spring Framework release before TuxCare onboarded version 6.1.4 (first TuxCare com...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22060"
      },
      "impact_statement": "not_affected \u2014 CVE-2021-22060 affects Spring Framework versions 5.3.0-5.3.13, 5.2.0-5.2.18, and older. The target version 6.1.4 is significantly newer and already contains the upstream vendor's fix (commit 99c7608ffe \"Replace both EOL and control characters\" by Rossen Stoyanchev @vmware.com). The fix was shipped in the upstream Spring Framework release before TuxCare onboarded version 6.1.4 (first TuxCare com..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-31T21:24:14.444573+00:00",
      "status_notes": "Vulnerability CVE-2021-22096 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2021-22096 (log injection vulnerability) is NOT present in Spring Framework 6.1.4. The fix was already shipped in the upstream 6.1.4 release. The target contains both the core sanitization logic (LogFormatUtils with NEWLINE_PATTERN and CONTROL_CHARACTER_PATTERN) and its application to user-facing logging locations. The vulnerable pattern (unsanitized user input in log statements) is not pre...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22096"
      },
      "impact_statement": "not_affected \u2014 CVE-2021-22096 (log injection vulnerability) is NOT present in Spring Framework 6.1.4. The fix was already shipped in the upstream 6.1.4 release. The target contains both the core sanitization logic (LogFormatUtils with NEWLINE_PATTERN and CONTROL_CHARACTER_PATTERN) and its application to user-facing logging locations. The vulnerable pattern (unsanitized user input in log statements) is not pre..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:18:58.233822+00:00",
      "status_notes": "Vulnerability CVE-2024-22233 does not affect version 6.1.4-tuxcare.2 of org.springframework:spring-core. Spring Framework 6.1.4 is NOT affected by CVE-2024-22233. Both vulnerability patterns (missing exception handling in ForwardedHeaderFilter and String.matches usage in HandlerMappingIntrospector) were fixed in upstream release v6.1.3, before v6.1.4 was released. The target inherited these fixes from the upstream Spring Framework release that TuxCare onboarded, making the vulnerable code patterns absent from the target version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 6.1.2, < 6.1.3; >= 6.0.15, < 6.0.16), NVD (= 6.0.15; = 6.1.2), cve.org (= 6.1.2; = 6.0.15), Snyk (>= 6.0.15, < 6.0.16; >= 6.1.2, < 6.1.3).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-22233"
      },
      "impact_statement": "Spring Framework 6.1.4 is NOT affected by CVE-2024-22233. Both vulnerability patterns (missing exception handling in ForwardedHeaderFilter and String.matches usage in HandlerMappingIntrospector) were fixed in upstream release v6.1.3, before v6.1.4 was released. The target inherited these fixes from the upstream Spring Framework release that TuxCare onboarded, making the vulnerable code patterns absent from the target version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 6.1.2, < 6.1.3; >= 6.0.15, < 6.0.16), NVD (= 6.0.15; = 6.1.2), cve.org (= 6.1.2; = 6.0.15), Snyk (>= 6.0.15, < 6.0.16; >= 6.1.2, < 6.1.3)."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-41249 is fixed in version 6.1.4-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2025-41249"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.4-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-21T16:35:00.322171+00:00",
      "status_notes": "Vulnerability CVE-2026-41848 affects version 6.1.4-tuxcare.2 of org.springframework:spring-core, and is fixed in 6.1.4-tuxcare.8.",
      "vulnerability": {
        "name": "CVE-2026-41848"
      },
      "action_statement": "Vulnerability CVE-2026-41848 affects version 6.1.4-tuxcare.2 of org.springframework:spring-core, and is fixed in 6.1.4-tuxcare.8."
    }
  ]
}