{
  "@id": "urn:uuid:cc77cdca-81a5-426c-8c35-4aade335ba39",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 49,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T04:25:00.091559+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T12:54:14.700427+00:00",
      "status_notes": "Vulnerability CVE-2009-1190 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. not_affected \u2014 CVE-2009-1190 affects Spring Framework versions 1.1.0-2.5.6 and 3.0.0.M1-M2 via deserialization of malicious regex patterns causing CPU exhaustion. The vulnerability was fixed upstream in commit 9306d6dbaa (April 20, 2009) by removing the readObject() method that recompiled patterns during deserialization. Spring 6.0.11-tuxcare.6 contains this fix, which shipped in the upstream release before T...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2009-1190"
      },
      "impact_statement": "not_affected \u2014 CVE-2009-1190 affects Spring Framework versions 1.1.0-2.5.6 and 3.0.0.M1-M2 via deserialization of malicious regex patterns causing CPU exhaustion. The vulnerability was fixed upstream in commit 9306d6dbaa (April 20, 2009) by removing the readObject() method that recompiled patterns during deserialization. Spring 6.0.11-tuxcare.6 contains this fix, which shipped in the upstream release before T..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-06T17:40:04.386984+00:00",
      "status_notes": "Vulnerability CVE-2011-2730 does not affect version 6.0.11-tuxcare.1 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.0.11 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.0.11 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.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T09:53:00.048327+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.0.11 is not affected by CVE-2011-2894. The vulnerability's attack vector\u2014RMI remoting classes (RemoteInvocationSerializingExporter, CodebaseAwareObjectInputStream) that deserialized untrusted objects\u2014was completely removed by upstream in commit 5822f1bf85 (Sept 2021), years before the 6.0.11 release that TuxCare onboarded. While ConfigurableObjectInputStream retains the 2011 ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.0.11 is not affected by CVE-2011-2894. The vulnerability's attack vector\u2014RMI remoting classes (RemoteInvocationSerializingExporter, CodebaseAwareObjectInputStream) that deserialized untrusted objects\u2014was completely removed by upstream in commit 5822f1bf85 (Sept 2021), years before the 6.0.11 release that TuxCare onboarded. While ConfigurableObjectInputStream retains the 2011 ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-02T17:10:00.096270+00:00",
      "status_notes": "Vulnerability CVE-2014-3578 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. not_affected \u2014 CVE-2014-3578 is NOT present in Spring Framework 6.0.11. The vulnerability was a directory traversal issue in StringUtils.cleanPath() that allowed attackers to read arbitrary files via crafted URLs containing colons followed by path traversal sequences (e.g., /a/:b/../../sensitive/file). The fix was introduced by upstream in Spring 3.2.9 and 4.0.5 (May 2014), and was already present in version ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-3578"
      },
      "impact_statement": "not_affected \u2014 CVE-2014-3578 is NOT present in Spring Framework 6.0.11. The vulnerability was a directory traversal issue in StringUtils.cleanPath() that allowed attackers to read arbitrary files via crafted URLs containing colons followed by path traversal sequences (e.g., /a/:b/../../sensitive/file). The fix was introduced by upstream in Spring 3.2.9 and 4.0.5 (May 2014), and was already present in version ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T19:19:36.318385+00:00",
      "status_notes": "Vulnerability CVE-2015-0201 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.0.11 is not affected by CVE-2015-0201. The vulnerable pattern (using AlternativeJdkIdGenerator for SockJS session ID generation) is not present. The target uses JdkIdGenerator which generates cryptographically unpredictable session IDs via UUID.randomUUID(). The fix was authored by upstream (rstoyanchev@pivotal.io) in commit 52b8f34 dated January 22, 2015, and was already inc...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-0201"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.0.11 is not affected by CVE-2015-0201. The vulnerable pattern (using AlternativeJdkIdGenerator for SockJS session ID generation) is not present. The target uses JdkIdGenerator which generates cryptographically unpredictable session IDs via UUID.randomUUID(). The fix was authored by upstream (rstoyanchev@pivotal.io) in commit 52b8f34 dated January 22, 2015, and was already inc..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T13:09:44.726673+00:00",
      "status_notes": "Vulnerability CVE-2015-5211 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. The target Spring Framework 6.0.11 is not affected by CVE-2015-5211 (Reflected File Download vulnerability). The upstream fix commit 2bd1daa75ee0b8ec33608ca6ab065ef3e1815543 from October 2015 was already present in the upstream 6.0.11 release when TuxCare onboarded it in August 2026. The defense mechanism (addContentDispositionHeader with SAFE_EXTENSIONS whitelist) is present and active in AbstractMessageConverterMethodProcessor, preventing responses from being downloaded with dangerous file extensions by adding a Content-Disposition header with safe filename when the URL contains non-whitelisted extensions.\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.0.11 is not affected by CVE-2015-5211 (Reflected File Download vulnerability). The upstream fix commit 2bd1daa75ee0b8ec33608ca6ab065ef3e1815543 from October 2015 was already present in the upstream 6.0.11 release when TuxCare onboarded it in August 2026. The defense mechanism (addContentDispositionHeader with SAFE_EXTENSIONS whitelist) is present and active in AbstractMessageConverterMethodProcessor, preventing responses from being downloaded with dangerous file extensions by adding a Content-Disposition header with safe filename when the URL contains non-whitelisted extensions.\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.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T13:18:44.496921+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. CVE-2016-5007 is not present in Spring Framework 6.0.11. The vulnerability was fixed by upstream commit a30ab30e4e (2016-04-25) which introduced the HandlerMapping introspection API. This fix was shipped in the upstream release and is present in the target version. The fix provides a standard API (MatchableHandlerMapping interface with match() methods) allowing Spring Security to use the same pattern matching logic as Spring MVC, preventing authorization bypass due to pattern matching discrepancies.\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 is not present in Spring Framework 6.0.11. The vulnerability was fixed by upstream commit a30ab30e4e (2016-04-25) which introduced the HandlerMapping introspection API. This fix was shipped in the upstream release and is present in the target version. The fix provides a standard API (MatchableHandlerMapping interface with match() methods) allowing Spring Security to use the same pattern matching logic as Spring MVC, preventing authorization bypass due to pattern matching discrepancies.\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.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T14:00:42.857553+00:00",
      "status_notes": "Vulnerability CVE-2018-11040 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. Spring Framework 6.0.11 is not affected by CVE-2018-11040. JSONP support was completely removed in upstream Spring Framework 6.x (commit ac37b678a3, June 7, 2018) before TuxCare onboarded version 6.0.11. The vulnerable code\u2014including MappingJackson2JsonView's jsonpParameterNames field, AbstractJsonpResponseBodyAdvice class, and all JSONP parameter processing logic\u2014does not exist in the target. The CVE affected Spring Framework 4.3.x < 4.3.18 and 5.0.x < 5.0.7; version 6.0.11 is a much newer release where the entire JSONP feature was architecturally removed upstream.\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 6.0.11 is not affected by CVE-2018-11040. JSONP support was completely removed in upstream Spring Framework 6.x (commit ac37b678a3, June 7, 2018) before TuxCare onboarded version 6.0.11. The vulnerable code\u2014including MappingJackson2JsonView's jsonpParameterNames field, AbstractJsonpResponseBodyAdvice class, and all JSONP parameter processing logic\u2014does not exist in the target. The CVE affected Spring Framework 4.3.x < 4.3.18 and 5.0.x < 5.0.7; version 6.0.11 is a much newer release where the entire JSONP feature was architecturally removed upstream.\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.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T01:15:16.880365+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.0.11 is not affected by CVE-2018-1199. The vulnerability affected versions 4.3.x before 4.3.14 and 5.0.x before 5.0.3 (2018), but version 6.0.11 (released July 2023) already includes the upstream fix. The defense mechanism (removeSemicolonContent = true by default in UrlPathHelper) strips path parameters before security constraint matching, preventing the bypass described in ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.0.11 is not affected by CVE-2018-1199. The vulnerability affected versions 4.3.x before 4.3.14 and 5.0.x before 5.0.3 (2018), but version 6.0.11 (released July 2023) already includes the upstream fix. The defense mechanism (removeSemicolonContent = true by default in UrlPathHelper) strips path parameters before security constraint matching, preventing the bypass described in ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T10:20:00.109102+00:00",
      "status_notes": "Vulnerability CVE-2018-1257 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1257 affects Spring Framework versions 5.0.x prior to 5.0.6, 4.3.x prior to 4.3.17, and older versions. The target is Spring Framework 6.0.11, which is significantly newer than the affected versions. The vulnerability allowed attackers to craft malicious STOMP subscription messages with selector headers containing regex patterns that could cause ReDoS attacks. The fix (commit ff2228fda...",
      "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, 4.3.x prior to 4.3.17, and older versions. The target is Spring Framework 6.0.11, which is significantly newer than the affected versions. The vulnerability allowed attackers to craft malicious STOMP subscription messages with selector headers containing regex patterns that could cause ReDoS attacks. The fix (commit ff2228fda..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2018-1258 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. Spring Framework 6.0.11 is not affected by CVE-2018-1258. The vulnerability was fixed by upstream Spring Framework in April 2018 (commits aa11721ff0 and eaff2c28a7), and these fixes were already included in the upstream 6.0.11 release that TuxCare onboarded. All vulnerable code patterns have been replaced with the fixed implementations across all affected files (AopUtils.java, AnnotationMethodMatcher.java, CacheAspectSupport.java, ApplicationListenerMethodAdapter.java).\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": "Spring Framework 6.0.11 is not affected by CVE-2018-1258. The vulnerability was fixed by upstream Spring Framework in April 2018 (commits aa11721ff0 and eaff2c28a7), and these fixes were already included in the upstream 6.0.11 release that TuxCare onboarded. All vulnerable code patterns have been replaced with the fixed implementations across all affected files (AopUtils.java, AnnotationMethodMatcher.java, CacheAspectSupport.java, ApplicationListenerMethodAdapter.java).\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.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T19:06:00.099940+00:00",
      "status_notes": "Vulnerability CVE-2018-1271 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.0.11-tuxcare.6 is not affected by CVE-2018-1271. The vulnerability (missing URL decoding before directory traversal checks in static resource handlers) was fixed in upstream Spring Framework in March 2018 via commit 91b803a2. This fix was already included in the upstream Spring Framework 6.0.11 release (July 2023) when TuxCare onboarded it. All affected components (PathResour...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1271"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.0.11-tuxcare.6 is not affected by CVE-2018-1271. The vulnerability (missing URL decoding before directory traversal checks in static resource handlers) was fixed in upstream Spring Framework in March 2018 via commit 91b803a2. This fix was already included in the upstream Spring Framework 6.0.11 release (July 2023) when TuxCare onboarded it. All affected components (PathResour..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T12:31:15.270922+00:00",
      "status_notes": "Vulnerability CVE-2018-1272 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. Spring Framework 6.0.11 is NOT vulnerable to CVE-2018-1272. The vulnerability involved predictable multipart boundary generation using java.util.Random, which allowed attackers to forge boundaries and inject malicious multipart content. The fix (using SecureRandom instead of Random) was applied by upstream Spring Framework in March 2018 (commit ab2410c754) and was already present in the Spring Framework 6.0.11 release when TuxCare onboarded it. The current code uses a lazy-initialized SecureRandom instance for all boundary generation, making boundaries cryptographically unpredictable and preventing boundary forgery attacks.\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.0.11 is NOT vulnerable to CVE-2018-1272. The vulnerability involved predictable multipart boundary generation using java.util.Random, which allowed attackers to forge boundaries and inject malicious multipart content. The fix (using SecureRandom instead of Random) was applied by upstream Spring Framework in March 2018 (commit ab2410c754) and was already present in the Spring Framework 6.0.11 release when TuxCare onboarded it. The current code uses a lazy-initialized SecureRandom instance for all boundary generation, making boundaries cryptographically unpredictable and preventing boundary forgery attacks.\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.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T13:44:47.079180+00:00",
      "status_notes": "Vulnerability CVE-2018-15756 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. The target Spring Framework 6.0.11 is NOT AFFECTED by CVE-2018-15756. The vulnerability (DoS via malicious HTTP Range headers with excessive ranges or overlapping ranges) was fixed in upstream commit 423aa28ed584b4ff6e5bad218c09beef5e91951e by Rossen Stoyanchev in October 2018. This fix was already present in the upstream 6.0.11 release that TuxCare onboarded, predating all TuxCare commits. Both required defenses are present and active: (1) MAX_RANGES=100 limit enforced in parseRanges(), and (2) validation that sum of all range bytes < resource length in toResourceRegions(). No configuration flags or bypass paths exist.\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.0.11 is NOT AFFECTED by CVE-2018-15756. The vulnerability (DoS via malicious HTTP Range headers with excessive ranges or overlapping ranges) was fixed in upstream commit 423aa28ed584b4ff6e5bad218c09beef5e91951e by Rossen Stoyanchev in October 2018. This fix was already present in the upstream 6.0.11 release that TuxCare onboarded, predating all TuxCare commits. Both required defenses are present and active: (1) MAX_RANGES=100 limit enforced in parseRanges(), and (2) validation that sum of all range bytes < resource length in toResourceRegions(). No configuration flags or bypass paths exist.\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.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-31T20:57:00.154151+00:00",
      "status_notes": "Vulnerability CVE-2021-22060 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.0.11 is not affected by CVE-2021-22060 (log injection via newline and control characters). The fix was already present in the upstream 6.0.11 release before TuxCare onboarded it. The vulnerability allowed attackers to inject fake log entries by providing malicious input containing newline (\\n, \\r) and control characters. The upstream fix (commit 99c7608ff by rstoyanchev@vmwar...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22060"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.0.11 is not affected by CVE-2021-22060 (log injection via newline and control characters). The fix was already present in the upstream 6.0.11 release before TuxCare onboarded it. The vulnerability allowed attackers to inject fake log entries by providing malicious input containing newline (\\n, \\r) and control characters. The upstream fix (commit 99c7608ff by rstoyanchev@vmwar..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-31T21:36:16.312368+00:00",
      "status_notes": "Vulnerability CVE-2021-22096 does not affect version 6.0.11-tuxcare.1 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.0.11 is not affected by CVE-2021-22096. The vulnerability was fixed by upstream Spring maintainer Rossen Stoyanchev in commit 99c7608ffe (December 2021), which predates the Spring Framework 6.0.x release series (November 2022). The fix was already present in the upstream release when TuxCare onboarded version 6.0.11. The target contains the complete mitigation: LogFormatUtils...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22096"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.0.11 is not affected by CVE-2021-22096. The vulnerability was fixed by upstream Spring maintainer Rossen Stoyanchev in commit 99c7608ffe (December 2021), which predates the Spring Framework 6.0.x release series (November 2022). The fix was already present in the upstream release when TuxCare onboarded version 6.0.11. The target contains the complete mitigation: LogFormatUtils..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-10T04:25:00.091559+00:00",
      "status_notes": "Vulnerability CVE-2024-22233 does not affect version 6.0.11-tuxcare.1 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 comparison is absent. In spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:166 and :187, requests are wrapped and mappings resolved directly; the helper at :209 parses the request path and iterates configured handlers without comparing cached URIs using regular expressions.",
      "justification": "vulnerable_code_not_in_execute_path",
      "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 comparison is absent. In spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:166 and :187, requests are wrapped and mappings resolved directly; the helper at :209 parses the request path and iterates configured handlers without comparing cached URIs using regular expressions."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-21T12:29:00.195526+00:00",
      "status_notes": "Vulnerability CVE-2025-41249 affects version 6.0.11-tuxcare.1 of org.springframework:spring-core, and is fixed in 6.0.11-tuxcare.6.",
      "vulnerability": {
        "name": "CVE-2025-41249"
      },
      "action_statement": "Vulnerability CVE-2025-41249 affects version 6.0.11-tuxcare.1 of org.springframework:spring-core, and is fixed in 6.0.11-tuxcare.6."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.11-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-21T12:29:00.195526+00:00",
      "status_notes": "Vulnerability CVE-2026-41848 affects version 6.0.11-tuxcare.1 of org.springframework:spring-core, and is fixed in 6.0.11-tuxcare.6.",
      "vulnerability": {
        "name": "CVE-2026-41848"
      },
      "action_statement": "Vulnerability CVE-2026-41848 affects version 6.0.11-tuxcare.1 of org.springframework:spring-core, and is fixed in 6.0.11-tuxcare.6."
    }
  ]
}