{
  "@id": "urn:uuid:e474cc51-771e-4cb6-8454-d8043c7fc8a3",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 50,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-06T17:30:26.757723+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-10-30T12:08:09.754749+00:00",
      "status_notes": "Vulnerability CVE-2009-1190 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 CVE-2009-1190 is a JDK-level algorithmic complexity vulnerability in Pattern.compile() affecting JDK versions before 1.6. Spring Framework 6.1.13 requires JDK 17 (confirmed in JavaConventions.java:74), which is 11 major versions beyond the fix. The underlying Pattern.compile vulnerability does not exist in JDK 17. While Spring's JdkRegexpMethodPointcut class remains Serializable and compiles re...",
      "vulnerability": {
        "name": "CVE-2009-1190"
      },
      "impact_statement": "not_affected \u2014 CVE-2009-1190 is a JDK-level algorithmic complexity vulnerability in Pattern.compile() affecting JDK versions before 1.6. Spring Framework 6.1.13 requires JDK 17 (confirmed in JavaConventions.java:74), which is 11 major versions beyond the fix. The underlying Pattern.compile vulnerability does not exist in JDK 17. While Spring's JdkRegexpMethodPointcut class remains Serializable and compiles re..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-06T17:30:26.757723+00:00",
      "status_notes": "Vulnerability CVE-2011-2730 does not affect version 6.1.13-tuxcare.4 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.13 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.13 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.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T09:38:00.146680+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.1.13 is not affected by CVE-2011-2894. The vulnerability affected versions 3.0.0-3.0.5, which lacked any mechanism to reject malicious proxy class deserialization. The fix (acceptProxyClasses flag in ConfigurableObjectInputStream.resolveProxyClass()) was added by upstream Spring Framework in July 2011 and is present in version 6.1.13. While the flag defaults to true (accepts ...",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.1.13 is not affected by CVE-2011-2894. The vulnerability affected versions 3.0.0-3.0.5, which lacked any mechanism to reject malicious proxy class deserialization. The fix (acceptProxyClasses flag in ConfigurableObjectInputStream.resolveProxyClass()) was added by upstream Spring Framework in July 2011 and is present in version 6.1.13. While the flag defaults to true (accepts ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-02T17:10:00.096270+00:00",
      "status_notes": "Vulnerability CVE-2014-3578 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 Target version 6.1.13 is NOT AFFECTED by CVE-2014-3578. The vulnerability (directory traversal via malformed paths containing colons like `/a/:b/../../file`) was fixed by upstream Spring Framework in May 2014 (commit 8ee4651038) by adding a check that prevents treating substrings-up-to-colon as removable prefixes when they contain path separators. This fix was already present in the upstream Sp...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-3578"
      },
      "impact_statement": "not_affected \u2014 Target version 6.1.13 is NOT AFFECTED by CVE-2014-3578. The vulnerability (directory traversal via malformed paths containing colons like `/a/:b/../../file`) was fixed by upstream Spring Framework in May 2014 (commit 8ee4651038) by adding a check that prevents treating substrings-up-to-colon as removable prefixes when they contain path separators. This fix was already present in the upstream Sp..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T19:05:46.375124+00:00",
      "status_notes": "Vulnerability CVE-2015-0201 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5 due to predictable session ID generation in the SockJS client. The vulnerability used AlternativeJdkIdGenerator which employed java.util.Random (predictable after initial seeding). The fix, introduced in Spring Framework 4.1.5 (January 2015), replaced it with JdkIdGenerator using UUID.randomUUID() (cryptographically secure). The target v...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-0201"
      },
      "impact_statement": "not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5 due to predictable session ID generation in the SockJS client. The vulnerability used AlternativeJdkIdGenerator which employed java.util.Random (predictable after initial seeding). The fix, introduced in Spring Framework 4.1.5 (January 2015), replaced it with JdkIdGenerator using UUID.randomUUID() (cryptographically secure). The target v..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T12:57:15.327260+00:00",
      "status_notes": "Vulnerability CVE-2015-5211 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. Spring Framework 6.1.13-tuxcare.4 is NOT vulnerable to CVE-2015-5211 (Reflected File Download). The RFD defense mechanism is present and active in the target. The fix was already included in the upstream Spring Framework 6.1.13 release (October 2015 original fix by Rossen Stoyanchev, further improved over time). TuxCare onboarded this version with the fix already present; no TuxCare backport was needed. The vulnerable pattern described in CVE-2015-5211 cannot manifest in this version.\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 6.1.13-tuxcare.4 is NOT vulnerable to CVE-2015-5211 (Reflected File Download). The RFD defense mechanism is present and active in the target. The fix was already included in the upstream Spring Framework 6.1.13 release (October 2015 original fix by Rossen Stoyanchev, further improved over time). TuxCare onboarded this version with the fix already present; no TuxCare backport was needed. The vulnerable pattern described in CVE-2015-5211 cannot manifest in this version.\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.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T13:08:56.260651+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. Spring Framework 6.1.13 is not affected by CVE-2016-5007. The vulnerability, which concerned inconsistent URL pattern matching between Spring Security and Spring MVC leading to potential authorization bypass, was fixed in Spring Framework 4.3.1 (April 2016) via commit a30ab30e4e. The fix introduced the HandlerMappingIntrospector and MatchableHandlerMapping interface, providing a standard API for authorization systems to use the same pattern matching logic as request routing. This fix was authored by the upstream Spring Framework team (rstoyanchev@pivotal.io) and was already present in the upstream 6.1.13 release when TuxCare onboarded it in August 2026. Both AbstractUrlHandlerMapping and RequestMappingHandlerMapping implement MatchableHandlerMapping with the match() method that exposes their internal pattern matching logic.\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 6.1.13 is not affected by CVE-2016-5007. The vulnerability, which concerned inconsistent URL pattern matching between Spring Security and Spring MVC leading to potential authorization bypass, was fixed in Spring Framework 4.3.1 (April 2016) via commit a30ab30e4e. The fix introduced the HandlerMappingIntrospector and MatchableHandlerMapping interface, providing a standard API for authorization systems to use the same pattern matching logic as request routing. This fix was authored by the upstream Spring Framework team (rstoyanchev@pivotal.io) and was already present in the upstream 6.1.13 release when TuxCare onboarded it in August 2026. Both AbstractUrlHandlerMapping and RequestMappingHandlerMapping implement MatchableHandlerMapping with the match() method that exposes their internal pattern matching logic.\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.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T13:51:14.737145+00:00",
      "status_notes": "Vulnerability CVE-2018-11040 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. Spring Framework 6.1.13 is not affected by CVE-2018-11040. The vulnerability concerned automatic JSONP support being enabled by default in MappingJackson2JsonView (versions 4.3.x < 4.3.18 and 5.0.x < 5.0.7). In upstream Spring Framework 5.1, JSONP support was completely removed (commit ac37b678a3, June 2018) by Sebastien Deleuze. Version 6.1.13 was onboarded by TuxCare after JSONP was already removed upstream, so the vulnerable code never existed in this version.\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.1.13 is not affected by CVE-2018-11040. The vulnerability concerned automatic JSONP support being enabled by default in MappingJackson2JsonView (versions 4.3.x < 4.3.18 and 5.0.x < 5.0.7). In upstream Spring Framework 5.1, JSONP support was completely removed (commit ac37b678a3, June 2018) by Sebastien Deleuze. Version 6.1.13 was onboarded by TuxCare after JSONP was already removed upstream, so the vulnerable code never existed in this version.\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.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T00:54:45.999289+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1199 is NOT present in Spring Framework 6.1.13. The vulnerability allowed bypassing security constraints via URL path parameters with special encodings (duplicate slashes, backslashes, URL-encoded traversal sequences). The fix added path normalization (processPath) and encoded path validation (isInvalidEncodedPath) to sanitize paths before resource resolution. All fixes were authored b...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1199 is NOT present in Spring Framework 6.1.13. The vulnerability allowed bypassing security constraints via URL path parameters with special encodings (duplicate slashes, backslashes, URL-encoded traversal sequences). The fix added path normalization (processPath) and encoded path validation (isInvalidEncodedPath) to sanitize paths before resource resolution. All fixes were authored b..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-10-30T09:01:17.494754+00:00",
      "status_notes": "Vulnerability CVE-2018-1257 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1257 is not present in Spring Framework 6.1.13. The vulnerability involved a ReDoS attack through malicious Spring EL expressions in STOMP subscription selector headers. The upstream Spring Framework 6.1 release already contains commit 5bc80fc094 (June 2023) by Sam Brannen that disables SpEL selector support by default. The selectorHeaderName field is now null by default in DefaultSubs...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1257"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1257 is not present in Spring Framework 6.1.13. The vulnerability involved a ReDoS attack through malicious Spring EL expressions in STOMP subscription selector headers. The upstream Spring Framework 6.1 release already contains commit 5bc80fc094 (June 2023) by Sam Brannen that disables SpEL selector support by default. The selectorHeaderName field is now null by default in DefaultSubs..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2018-1258 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. Spring Framework 6.1.13 is not affected by CVE-2018-1258. The vulnerability was an authorization bypass caused by improper method resolution on JDK dynamic proxies, preventing security annotations from being discovered. The upstream fix (commit aa11721ff0, April 2018) was already present in Spring Framework 6.1.13 when TuxCare onboarded it. The fix removed the `!Proxy.isProxyClass()` check from AopUtils.getMostSpecificMethod(), enabling proper annotation discovery on proxied methods. Code inspection confirms the vulnerable pattern is absent from the target.\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.1.13 is not affected by CVE-2018-1258. The vulnerability was an authorization bypass caused by improper method resolution on JDK dynamic proxies, preventing security annotations from being discovered. The upstream fix (commit aa11721ff0, April 2018) was already present in Spring Framework 6.1.13 when TuxCare onboarded it. The fix removed the `!Proxy.isProxyClass()` check from AopUtils.getMostSpecificMethod(), enabling proper annotation discovery on proxied methods. Code inspection confirms the vulnerable pattern is absent from the target.\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.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-10-30T18:27:28.153921+00:00",
      "status_notes": "Vulnerability CVE-2018-1271 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.1.13 includes the upstream fix for CVE-2018-1271. The vulnerability allowed directory traversal via URL-encoded paths (e.g., %2E%2E for ..) when serving static resources from Windows file systems. The fix adds isInvalidEncodedPath() methods that URL-decode request paths and reject those containing ../ or ..\\ sequences. This fix was introduced in upstream commit 91b803a231 (Ma...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1271"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.1.13 includes the upstream fix for CVE-2018-1271. The vulnerability allowed directory traversal via URL-encoded paths (e.g., %2E%2E for ..) when serving static resources from Windows file systems. The fix adds isInvalidEncodedPath() methods that URL-decode request paths and reject those containing ../ or ..\\ sequences. This fix was introduced in upstream commit 91b803a231 (Ma..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T12:19:18.164920+00:00",
      "status_notes": "Vulnerability CVE-2018-1272 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. Spring Framework 6.1.13 is not affected by CVE-2018-1272. The vulnerability (predictable multipart boundaries due to weak Random) was fixed in the upstream release before TuxCare onboarded it. The code uses SecureRandom for boundary generation (MimeTypeUtils.java:408).\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.13 is not affected by CVE-2018-1272. The vulnerability (predictable multipart boundaries due to weak Random) was fixed in the upstream release before TuxCare onboarded it. The code uses SecureRandom for boundary generation (MimeTypeUtils.java:408).\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.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T13:32:59.098532+00:00",
      "status_notes": "Vulnerability CVE-2018-15756 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. CVE-2018-15756 is not present in Spring Framework 6.1.13. The vulnerability concerned HTTP Range header DoS attacks via excessive range counts or overlapping ranges. The upstream fix (commit 423aa28ed5 by rstoyanchev@pivotal.io) shipped with Spring Framework 6.1.13 before TuxCare onboarded this version. The fix adds two defenses: (1) MAX_RANGES=100 limit rejecting Range headers with >100 ranges, and (2) validation rejecting multi-range requests where sum of range byte-counts >= resource length. Both defenses are present and active in the target at spring-web/src/main/java/org/springframework/http/HttpRange.java.\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 6.1.13. The vulnerability concerned HTTP Range header DoS attacks via excessive range counts or overlapping ranges. The upstream fix (commit 423aa28ed5 by rstoyanchev@pivotal.io) shipped with Spring Framework 6.1.13 before TuxCare onboarded this version. The fix adds two defenses: (1) MAX_RANGES=100 limit rejecting Range headers with >100 ranges, and (2) validation rejecting multi-range requests where sum of range byte-counts >= resource length. Both defenses are present and active in the target at spring-web/src/main/java/org/springframework/http/HttpRange.java.\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.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-10-31T20:17:11.693922+00:00",
      "status_notes": "Vulnerability CVE-2021-22060 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 CVE-2021-22060 (log injection vulnerability) is not present in Spring Framework 6.1.13-tuxcare.4. The vulnerability allowed attackers to inject malicious input containing newline and control characters into log messages, creating additional log entries or manipulating log output. The upstream fix, authored by Rossen Stoyanchev (rstoyanchev@vmware.com), was already included in Spring Framework 6...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22060"
      },
      "impact_statement": "not_affected \u2014 CVE-2021-22060 (log injection vulnerability) is not present in Spring Framework 6.1.13-tuxcare.4. The vulnerability allowed attackers to inject malicious input containing newline and control characters into log messages, creating additional log entries or manipulating log output. The upstream fix, authored by Rossen Stoyanchev (rstoyanchev@vmware.com), was already included in Spring Framework 6..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-10-31T21:17:59.645329+00:00",
      "status_notes": "Vulnerability CVE-2021-22096 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 Target version 6.1.13 is NOT vulnerable to CVE-2021-22096 (log injection). The complete fix was authored by upstream Spring developer Rossen Stoyanchev (commit 99c7608ff, Dec 2021) and shipped in the upstream release that TuxCare onboarded. The fix includes: (1) LogFormatUtils.formatValue() sanitizing newlines to <EOL> and control characters to ? (spring-core/src/main/java/org/springframework/c...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22096"
      },
      "impact_statement": "not_affected \u2014 Target version 6.1.13 is NOT vulnerable to CVE-2021-22096 (log injection). The complete fix was authored by upstream Spring developer Rossen Stoyanchev (commit 99c7608ff, Dec 2021) and shipped in the upstream release that TuxCare onboarded. The fix includes: (1) LogFormatUtils.formatValue() sanitizing newlines to <EOL> and control characters to ? (spring-core/src/main/java/org/springframework/c..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-04T09:18:58.233822+00:00",
      "status_notes": "Vulnerability CVE-2024-22233 does not affect version 6.1.13-tuxcare.4 of org.springframework:spring-core. Target Spring Framework 6.1.13 is not affected by CVE-2024-22233. Both vulnerability fixes are already present from upstream release 6.1.3: (1) ForwardedHeaderFilter has exception handling to catch malformed header parsing errors and return HTTP 400, preventing DoS via IllegalArgumentException/IllegalStateException, and (2) HandlerMappingIntrospector uses String.equals() instead of String.matches() for URI comparison, preventing DoS via PatternSyntaxException on regex special characters. The CVE affected versions 6.0.15 and 6.1.2, which were fixed in 6.0.16 and 6.1.3 respectively. The target version 6.1.13 is 10 releases newer than the fixed 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": "Target Spring Framework 6.1.13 is not affected by CVE-2024-22233. Both vulnerability fixes are already present from upstream release 6.1.3: (1) ForwardedHeaderFilter has exception handling to catch malformed header parsing errors and return HTTP 400, preventing DoS via IllegalArgumentException/IllegalStateException, and (2) HandlerMappingIntrospector uses String.equals() instead of String.matches() for URI comparison, preventing DoS via PatternSyntaxException on regex special characters. The CVE affected versions 6.0.15 and 6.1.2, which were fixed in 6.0.16 and 6.1.3 respectively. The target version 6.1.13 is 10 releases newer than the fixed 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.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-10-21T12:02:40.835607+00:00",
      "status_notes": "Vulnerability CVE-2025-41249 is fixed in version 6.1.13-tuxcare.4 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2025-41249"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.1.13-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-10-21T12:03:00.097495+00:00",
      "status_notes": "Vulnerability CVE-2026-41848 is fixed in version 6.1.13-tuxcare.4 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2026-41848"
      }
    }
  ]
}