{
  "@id": "urn:uuid:c167e937-5230-4131-ba13-1949caa471e2",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 49,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T04:22:46.193289+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-10-30T12:09:48.333130+00:00",
      "status_notes": "Vulnerability CVE-2009-1190 does not affect version 5.2.13.RELEASE-tuxcare.6 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 when deserializing regex patterns. The vulnerability was fixed upstream in commit 9306d6dbaab (April 2009) by removing the readObject() method that recompiled patterns during deserialization. Target version 5.2.13.RELEASE contains this fix\u2014the vulnerable code pattern (readObject() calling Pattern.compile() on deserializ...",
      "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 when deserializing regex patterns. The vulnerability was fixed upstream in commit 9306d6dbaab (April 2009) by removing the readObject() method that recompiled patterns during deserialization. Target version 5.2.13.RELEASE contains this fix\u2014the vulnerable code pattern (readObject() calling Pattern.compile() on deserializ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-06T17:30:50.523713+00:00",
      "status_notes": "Vulnerability CVE-2011-2730 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. Prechecker: No vulnerable code from the fix was found, and the functions the fix changes were not found in this version. Version 5.2.13.RELEASE is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-wv88-pf73-x22p (affected up to 3.0.6), NVD (affected up to 3.0.5), Snyk (affected up to 3.0.6).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2730"
      },
      "impact_statement": "Prechecker: No vulnerable code from the fix was found, and the functions the fix changes were not found in this version. Version 5.2.13.RELEASE is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-wv88-pf73-x22p (affected up to 3.0.6), NVD (affected up to 3.0.5), Snyk (affected up to 3.0.6)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T09:38:00.146680+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. not_affected \u2014 The target repository (Spring Framework 5.2.13.RELEASE-tuxcare.12) is not affected by CVE-2011-2894. The vulnerability was fixed by upstream Spring Framework in July 2011 by adding an acceptProxyClasses configuration flag that allows blocking proxy class deserialization. This fix was already present in the upstream Spring Framework 5.2.13.RELEASE when TuxCare onboarded it. The fix was authored ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 The target repository (Spring Framework 5.2.13.RELEASE-tuxcare.12) is not affected by CVE-2011-2894. The vulnerability was fixed by upstream Spring Framework in July 2011 by adding an acceptProxyClasses configuration flag that allows blocking proxy class deserialization. This fix was already present in the upstream Spring Framework 5.2.13.RELEASE when TuxCare onboarded it. The fix was authored ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-02T17:10:00.096270+00:00",
      "status_notes": "Vulnerability CVE-2014-3578 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. not_affected \u2014 CVE-2014-3578 directory traversal vulnerability is NOT present in Spring Framework 5.2.13.RELEASE-tuxcare.12. The fix was shipped in the upstream release by Pivotal/Spring. The vulnerable code pattern (incorrect prefix handling in StringUtils.cleanPath that allowed directory traversal via paths like /a/:b/../../) has been replaced with defensive logic that discards prefixes containing '/' chara...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-3578"
      },
      "impact_statement": "not_affected \u2014 CVE-2014-3578 directory traversal vulnerability is NOT present in Spring Framework 5.2.13.RELEASE-tuxcare.12. The fix was shipped in the upstream release by Pivotal/Spring. The vulnerable code pattern (incorrect prefix handling in StringUtils.cleanPath that allowed directory traversal via paths like /a/:b/../../) has been replaced with defensive logic that discards prefixes containing '/' chara..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T19:06:19.212631+00:00",
      "status_notes": "Vulnerability CVE-2015-0201 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5 where the SockJS client used AlternativeJdkIdGenerator (predictable java.util.Random seeded once) for session IDs. The target version 5.2.13.RELEASE contains the upstream security fix from January 2015 (commit 52b8f34468) which replaced the vulnerable generator with JdkIdGenerator using UUID.randomUUID() (cryptographically secure). The f...",
      "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 SockJS client used AlternativeJdkIdGenerator (predictable java.util.Random seeded once) for session IDs. The target version 5.2.13.RELEASE contains the upstream security fix from January 2015 (commit 52b8f34468) which replaced the vulnerable generator with JdkIdGenerator using UUID.randomUUID() (cryptographically secure). The f..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T12:58:17.463230+00:00",
      "status_notes": "Vulnerability CVE-2015-5211 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. CVE-2015-5211 (Reflected File Download attack) is NOT present in Spring Framework 5.2.13.RELEASE-tuxcare.11. The upstream fix (commit 2bd1daa75e \"Protect against RFD exploits\" by Rossen Stoyanchev) was introduced in Spring Framework v4.2.2.RELEASE (October 2015) and is present in the 5.2.13.RELEASE that TuxCare onboarded. The defense mechanism in AbstractMessageConverterMethodProcessor.addContentDispositionHeader() (lines 406-444) adds a Content-Disposition header with a safe filename when the URL contains non-whitelisted extensions, preventing browsers from executing downloaded content. This is an upstream vendor fix that shipped before TuxCare's first commit (f1f23e2e57).\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": "CVE-2015-5211 (Reflected File Download attack) is NOT present in Spring Framework 5.2.13.RELEASE-tuxcare.11. The upstream fix (commit 2bd1daa75e \"Protect against RFD exploits\" by Rossen Stoyanchev) was introduced in Spring Framework v4.2.2.RELEASE (October 2015) and is present in the 5.2.13.RELEASE that TuxCare onboarded. The defense mechanism in AbstractMessageConverterMethodProcessor.addContentDispositionHeader() (lines 406-444) adds a Content-Disposition header with a safe filename when the URL contains non-whitelisted extensions, preventing browsers from executing downloaded content. This is an upstream vendor fix that shipped before TuxCare's first commit (f1f23e2e57).\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.2.0, < 4.2.2; >= 4.0.0, < 4.1.8; < 3.2.15), NVD (= 3.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.0; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.2.0; = 4.2.1), Snyk (>= 3.2.0.RELEASE, < 3.2.15.RELEASE; >= 4.0.0.RELEASE, < 4.1.8.RELEASE; >= 4.2.0.RELEASE, < 4.2.2.RELEASE; <= 0; <= 0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T13:09:44.726673+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. Target Spring Framework 5.2.13.RELEASE is NOT AFFECTED by CVE-2016-5007. The complete fix (HandlerMappingIntrospector API) was introduced in upstream Spring Framework 4.3.1.RELEASE (June 2016) and was already present in v5.2.13.RELEASE when TuxCare onboarded this version. The fix provides introspection API allowing Spring Security to use the same URL pattern matching logic as Spring MVC, eliminating the authorization bypass vulnerability.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.1), NVD (= 3.2.0; = 4.0.0; = 4.1.0; = 4.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 3.2.15; = 3.2.16; = 3.2.17; = 3.2.18; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.1.8; = 4.1.9; = 4.2.1; = 4.2.2; = 4.2.3; = 4.2.4; = 4.2.5; = 4.2.6; = 4.2.7; = 4.2.8; = 4.2.9), cve.org (>= 3.2, < 3.3; >= 4.0, < 4.1; >= 4.1, < 4.2; >= 4.2, < 4.3; < 3.2), Snyk (>= 3.2.0.RELEASE, < 4.3.1.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-5007"
      },
      "impact_statement": "Target Spring Framework 5.2.13.RELEASE is NOT AFFECTED by CVE-2016-5007. The complete fix (HandlerMappingIntrospector API) was introduced in upstream Spring Framework 4.3.1.RELEASE (June 2016) and was already present in v5.2.13.RELEASE when TuxCare onboarded this version. The fix provides introspection API allowing Spring Security to use the same URL pattern matching logic as Spring MVC, eliminating the authorization bypass vulnerability.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.1), NVD (= 3.2.0; = 4.0.0; = 4.1.0; = 4.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 3.2.15; = 3.2.16; = 3.2.17; = 3.2.18; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.1.8; = 4.1.9; = 4.2.1; = 4.2.2; = 4.2.3; = 4.2.4; = 4.2.5; = 4.2.6; = 4.2.7; = 4.2.8; = 4.2.9), cve.org (>= 3.2, < 3.3; >= 4.0, < 4.1; >= 4.1, < 4.2; >= 4.2, < 4.3; < 3.2), Snyk (>= 3.2.0.RELEASE, < 4.3.1.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T13:52:02.256694+00:00",
      "status_notes": "Vulnerability CVE-2018-11040 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. The target repository (Spring Framework 5.2.13.RELEASE) is not affected by CVE-2018-11040. JSONP support, which enabled the cross-domain vulnerability, was completely removed from the Spring Framework codebase in commit ac37b678a3 (June 2018) by upstream author Sebastien Deleuze. This removal was already present in the upstream 5.2.13.RELEASE before TuxCare's initial setup. The vulnerable code patterns (MappingJackson2JsonView.jsonpParameterNames field, AbstractJsonpResponseBodyAdvice class, JSONP transport handlers) are absent from the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE), NVD (< 4.3.18; >= 5.0.0, < 5.0.7), cve.org (>= 5.0.x, < 5.0.7; >= 4.3.x, < 4.3.18), Snyk (>= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-11040"
      },
      "impact_statement": "The target repository (Spring Framework 5.2.13.RELEASE) is not affected by CVE-2018-11040. JSONP support, which enabled the cross-domain vulnerability, was completely removed from the Spring Framework codebase in commit ac37b678a3 (June 2018) by upstream author Sebastien Deleuze. This removal was already present in the upstream 5.2.13.RELEASE before TuxCare's initial setup. The vulnerable code patterns (MappingJackson2JsonView.jsonpParameterNames field, AbstractJsonpResponseBodyAdvice class, JSONP transport handlers) are absent from the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE), NVD (< 4.3.18; >= 5.0.0, < 5.0.7), cve.org (>= 5.0.x, < 5.0.7; >= 4.3.x, < 4.3.18), Snyk (>= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T00:55:00.856051+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. not_affected \u2014 Target Spring Framework 5.2.13.RELEASE-tuxcare.12 is NOT affected by CVE-2018-1199. The vulnerability (path traversal via specially encoded URL parameters bypassing security constraints) was fixed in upstream Spring Framework versions 4.3.14 and 5.0.3. The target version 5.2.13.RELEASE already contains the complete fix (SPR-16616) authored by Rossen Stoyanchev from Pivotal, which was shipped in...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 Target Spring Framework 5.2.13.RELEASE-tuxcare.12 is NOT affected by CVE-2018-1199. The vulnerability (path traversal via specially encoded URL parameters bypassing security constraints) was fixed in upstream Spring Framework versions 4.3.14 and 5.0.3. The target version 5.2.13.RELEASE already contains the complete fix (SPR-16616) authored by Rossen Stoyanchev from Pivotal, which was shipped in..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-10-30T09:01:17.494754+00:00",
      "status_notes": "Vulnerability CVE-2018-1257 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. not_affected \u2014 The target Spring Framework 5.2.13.RELEASE is not affected by CVE-2018-1257. The vulnerability's fix was already present in the upstream release that TuxCare onboarded. The fix (commit ff2228fdaf by Rossen Stoyanchev) allows the selector header feature to be disabled by setting selectorHeaderName to null, and wraps all expression parsing in a null check. This defense prevents the regex DoS atta...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1257"
      },
      "impact_statement": "not_affected \u2014 The target Spring Framework 5.2.13.RELEASE is not affected by CVE-2018-1257. The vulnerability's fix was already present in the upstream release that TuxCare onboarded. The fix (commit ff2228fdaf by Rossen Stoyanchev) allows the selector header feature to be disabled by setting selectorHeaderName to null, and wraps all expression parsing in a null check. This defense prevents the regex DoS atta..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-04T09:18:58.233822+00:00",
      "status_notes": "Vulnerability CVE-2018-1258 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. CVE-2018-1258 describes an authorization bypass vulnerability in Spring Framework 5.0.5 when used with Spring Security method-level security. The vulnerability was caused by improper method resolution on proxy classes, where AopUtils.getMostSpecificMethod incorrectly excluded proxy classes from processing (via a !Proxy.isProxyClass check), causing security annotations to be checked on the wrong method. The target repository (Spring Framework 5.2.13.RELEASE-tuxcare.12) is NOT AFFECTED because the upstream fix was already included in version 5.2.13.RELEASE when it was released in February 2021, nearly 3 years after the vulnerability was fixed in April 2018. TuxCare onboarded an already-patched upstream release.\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 vulnerability in Spring Framework 5.0.5 when used with Spring Security method-level security. The vulnerability was caused by improper method resolution on proxy classes, where AopUtils.getMostSpecificMethod incorrectly excluded proxy classes from processing (via a !Proxy.isProxyClass check), causing security annotations to be checked on the wrong method. The target repository (Spring Framework 5.2.13.RELEASE-tuxcare.12) is NOT AFFECTED because the upstream fix was already included in version 5.2.13.RELEASE when it was released in February 2021, nearly 3 years after the vulnerability was fixed in April 2018. TuxCare onboarded an already-patched upstream release.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.5.RELEASE, < 5.0.6.RELEASE), NVD (= 5.0.5), cve.org (= 5.0.5), Snyk (>= 5.0.5.RELEASE, < 5.0.6.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-10-30T18:29:05.302173+00:00",
      "status_notes": "Vulnerability CVE-2018-1271 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1271 (directory traversal via URL-encoded path sequences in Spring MVC static resource handling) is NOT present in Spring Framework 5.2.13.RELEASE. The upstream fix was already included in the release that TuxCare onboarded. The fix adds `isInvalidEncodedPath()` validation that URL-decodes request paths and rejects those containing `../` or `..\\` directory traversal patterns, preventin...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1271"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1271 (directory traversal via URL-encoded path sequences in Spring MVC static resource handling) is NOT present in Spring Framework 5.2.13.RELEASE. The upstream fix was already included in the release that TuxCare onboarded. The fix adds `isInvalidEncodedPath()` validation that URL-decodes request paths and rejects those containing `../` or `..\\` directory traversal patterns, preventin..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T12:20:19.402749+00:00",
      "status_notes": "Vulnerability CVE-2018-1272 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. The target Spring Framework 5.2.13.RELEASE is not affected by CVE-2018-1272. The vulnerability involved predictable multipart boundary generation using weak java.util.Random, which allowed attackers to inject malicious multipart content by predicting boundary strings. The upstream fix (commit ab2410c754 by Rossen Stoyanchev, March 2018) replaced Random with SecureRandom in MimeTypeUtils.generateMultipartBoundary(), making boundaries cryptographically unpredictable. This fix was part of the upstream 5.2.13.RELEASE that TuxCare onboarded, predating the first TuxCare commit (f1f23e2e). The target's current code uses SecureRandom with lazy initialization (further improved in commit 847202c8f8), and all production code paths for multipart boundary generation route through the fixed MimeTypeUtils method.\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": "The target Spring Framework 5.2.13.RELEASE is not affected by CVE-2018-1272. The vulnerability involved predictable multipart boundary generation using weak java.util.Random, which allowed attackers to inject malicious multipart content by predicting boundary strings. The upstream fix (commit ab2410c754 by Rossen Stoyanchev, March 2018) replaced Random with SecureRandom in MimeTypeUtils.generateMultipartBoundary(), making boundaries cryptographically unpredictable. This fix was part of the upstream 5.2.13.RELEASE that TuxCare onboarded, predating the first TuxCare commit (f1f23e2e). The target's current code uses SecureRandom with lazy initialization (further improved in commit 847202c8f8), and all production code paths for multipart boundary generation route through the fixed MimeTypeUtils method.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.15; >= 5.0.0, < 5.0.5), NVD (>= 4.3.0, < 4.3.15; >= 5.0, < 5.0.5), cve.org (< 5.0.5; < 4.3.15), Snyk (>= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; >= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; <= 0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-03T13:33:56.225785+00:00",
      "status_notes": "Vulnerability CVE-2018-15756 does not affect version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core. The target Spring Framework 5.2.13.RELEASE is not affected by CVE-2018-15756. The vulnerability fix was already present in the upstream v5.2.13.RELEASE release before TuxCare onboarded it. All three required defenses are present and active: (1) MAX_RANGES constant limiting requests to 100 ranges, (2) range count validation in parseRanges(), and (3) sum-of-ranges validation in toResourceRegions(). The fix was authored by upstream Spring Framework (rstoyanchev@pivotal.io) in October 2018 and shipped with the upstream release, not backported by TuxCare.\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 5.2.13.RELEASE is not affected by CVE-2018-15756. The vulnerability fix was already present in the upstream v5.2.13.RELEASE release before TuxCare onboarded it. All three required defenses are present and active: (1) MAX_RANGES constant limiting requests to 100 ranges, (2) range count validation in parseRanges(), and (3) sum-of-ranges validation in toResourceRegions(). The fix was authored by upstream Spring Framework (rstoyanchev@pivotal.io) in October 2018 and shipped with the upstream release, not backported by TuxCare.\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": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2021-22060 is fixed in version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2021-22060"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2021-22096 is fixed in version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2021-22096"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-11-10T04:22:46.193289+00:00",
      "status_notes": "Vulnerability CVE-2024-22233 does not affect version 5.2.13.RELEASE-tuxcare.6 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 URI comparison is absent. In spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:124 and :142, getMatchableHandlerMapping and getCorsConfiguration independently iterate handler mappings without CachedResult or a cached URI comparison.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-22233"
      },
      "impact_statement": "Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version is not affected because the vulnerable cached URI comparison is absent. In spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:124 and :142, getMatchableHandlerMapping and getCorsConfiguration independently iterate handler mappings without CachedResult or a cached URI comparison."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-41249 affects version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core, and is fixed in 5.2.13.RELEASE-tuxcare.10.",
      "vulnerability": {
        "name": "CVE-2025-41249"
      },
      "action_statement": "Vulnerability CVE-2025-41249 affects version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core, and is fixed in 5.2.13.RELEASE-tuxcare.10."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.13.RELEASE-tuxcare.6"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-41848 affects version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core, and is fixed in 5.2.13.RELEASE-tuxcare.11.",
      "vulnerability": {
        "name": "CVE-2026-41848"
      },
      "action_statement": "Vulnerability CVE-2026-41848 affects version 5.2.13.RELEASE-tuxcare.6 of org.springframework:spring-core, and is fixed in 5.2.13.RELEASE-tuxcare.11."
    }
  ]
}