{
  "@id": "urn:uuid:444e6d30-687b-4c36-b4cb-e68cd09d7dc9",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 45,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T04:24:00.586682+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-10-30T12:43:41.326706+00:00",
      "status_notes": "Vulnerability CVE-2009-1190 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 CVE-2009-1190 affects Spring Framework 1.1.0 through 2.5.6 and 3.0.0.M1 through 3.0.0.M2. The target (Spring 5.1.6.RELEASE) contains the upstream fix from commit 9306d6dbaa (April 2009) which removed the vulnerable deserialization pattern. The fix changed Pattern arrays from transient to non-transient and removed the readObject method that recompiled regex patterns during deserialization, elimi...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2009-1190"
      },
      "impact_statement": "not_affected \u2014 CVE-2009-1190 affects Spring Framework 1.1.0 through 2.5.6 and 3.0.0.M1 through 3.0.0.M2. The target (Spring 5.1.6.RELEASE) contains the upstream fix from commit 9306d6dbaa (April 2009) which removed the vulnerable deserialization pattern. The fix changed Pattern arrays from transient to non-transient and removed the readObject method that recompiled regex patterns during deserialization, elimi..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-06T17:38:27.865569+00:00",
      "status_notes": "Vulnerability CVE-2011-2730 does not affect version 5.1.6.RELEASE-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 5.1.6.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.1.6.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.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T09:50:00.107701+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 Spring Framework 5.1.6.RELEASE is not affected by CVE-2011-2894. The vulnerability affected versions 3.0.0-3.0.5, which lacked any protection against malicious proxy class deserialization. The fix (acceptProxyClasses flag) was applied by upstream Spring in 2011 and has been part of the codebase for 8 years before version 5.1.6.RELEASE (2019). The target contains the complete fix logic in Config...",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 5.1.6.RELEASE is not affected by CVE-2011-2894. The vulnerability affected versions 3.0.0-3.0.5, which lacked any protection against malicious proxy class deserialization. The fix (acceptProxyClasses flag) was applied by upstream Spring in 2011 and has been part of the codebase for 8 years before version 5.1.6.RELEASE (2019). The target contains the complete fix logic in Config..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-02T17:10:00.096270+00:00",
      "status_notes": "Vulnerability CVE-2014-3578 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 The target Spring Framework 5.1.6.RELEASE is not affected by CVE-2014-3578. The vulnerability was a directory traversal issue in StringUtils.cleanPath() allowing crafted URLs with colons after path separators (e.g., `/a/:b/../../file`) to bypass normalization. The fix adds validation to reject path prefixes containing \"/\" characters. This fix was committed to upstream Spring Framework by Rossen...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-3578"
      },
      "impact_statement": "not_affected \u2014 The target Spring Framework 5.1.6.RELEASE is not affected by CVE-2014-3578. The vulnerability was a directory traversal issue in StringUtils.cleanPath() allowing crafted URLs with colons after path separators (e.g., `/a/:b/../../file`) to bypass normalization. The fix adds validation to reject path prefixes containing \"/\" characters. This fix was committed to upstream Spring Framework by Rossen..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T19:14:03.234394+00:00",
      "status_notes": "Vulnerability CVE-2015-0201 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5 where the Java SockJS client generated predictable session IDs. The target version 5.1.6.RELEASE is not affected because the fix was already present in the upstream Spring Framework release. The secure session ID generation using JdkIdGenerator (which uses UUID.randomUUID() with cryptographically secure randomness) was introduced in Spri...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-0201"
      },
      "impact_statement": "not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5 where the Java SockJS client generated predictable session IDs. The target version 5.1.6.RELEASE is not affected because the fix was already present in the upstream Spring Framework release. The secure session ID generation using JdkIdGenerator (which uses UUID.randomUUID() with cryptographically secure randomness) was introduced in Spri..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T13:06:45.482707+00:00",
      "status_notes": "Vulnerability CVE-2015-5211 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. Spring Framework 5.1.6.RELEASE already contains the upstream fix for CVE-2015-5211 (Reflected File Download). The fix was originally committed by the Spring/Pivotal team in October 2015 (commit 2bd1daa75e) and first released in v4.2.2.RELEASE. Since 5.1.6.RELEASE was released years later (2019), it inherently includes this protection. The target contains the complete defense mechanism: addContentDispositionHeader method in AbstractMessageConverterMethodProcessor that validates file extensions and adds Content-Disposition headers for unsafe 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": "Spring Framework 5.1.6.RELEASE already contains the upstream fix for CVE-2015-5211 (Reflected File Download). The fix was originally committed by the Spring/Pivotal team in October 2015 (commit 2bd1daa75e) and first released in v4.2.2.RELEASE. Since 5.1.6.RELEASE was released years later (2019), it inherently includes this protection. The target contains the complete defense mechanism: addContentDispositionHeader method in AbstractMessageConverterMethodProcessor that validates file extensions and adds Content-Disposition headers for unsafe 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@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T13:17:11.201920+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. Target version 5.1.6.RELEASE is not affected by CVE-2016-5007. The vulnerability concerned pattern matching inconsistencies between Spring Security and Spring Framework that could allow security bypasses when paths with special formatting (e.g., spaces) were matched differently by the two systems. The fix, introduced in Spring Framework 4.3.1 via commit a30ab30e by Rossen Stoyanchev (upstream), provides a MatchableHandlerMapping interface and HandlerMappingIntrospector class that allow Spring Security to use the exact same pattern matching logic as Spring MVC. This fix was already present in the upstream Spring Framework 5.1.6.RELEASE when TuxCare onboarded it (commit 381171eb54 by askorik@cloudlinux.com). The vulnerable code pattern is not present in this version.\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 version 5.1.6.RELEASE is not affected by CVE-2016-5007. The vulnerability concerned pattern matching inconsistencies between Spring Security and Spring Framework that could allow security bypasses when paths with special formatting (e.g., spaces) were matched differently by the two systems. The fix, introduced in Spring Framework 4.3.1 via commit a30ab30e by Rossen Stoyanchev (upstream), provides a MatchableHandlerMapping interface and HandlerMappingIntrospector class that allow Spring Security to use the exact same pattern matching logic as Spring MVC. This fix was already present in the upstream Spring Framework 5.1.6.RELEASE when TuxCare onboarded it (commit 381171eb54 by askorik@cloudlinux.com). The vulnerable code pattern is not present in this version.\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.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T13:58:58.947122+00:00",
      "status_notes": "Vulnerability CVE-2018-11040 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. CVE-2018-11040 affects Spring Framework 5.0.x prior to 5.0.7 and 4.3.x prior to 4.3.18 due to automatic JSONP support in MappingJackson2JsonView. The target version 5.1.6.RELEASE is NOT affected because all JSONP support was completely removed by upstream vendor (Spring/Pivotal) in commit ac37b678a3 on June 7, 2018, which shipped in Spring Framework 5.1.0.RC1 and all subsequent 5.1.x releases. The vulnerable code (jsonpParameterNames field, AbstractJsonpResponseBodyAdvice class, and all JSONP-related methods) does not exist in this version. This was an upstream fix that predates TuxCare's onboarding of version 5.1.6.RELEASE.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE), NVD (< 4.3.18; >= 5.0.0, < 5.0.7), cve.org (>= 5.0.x, < 5.0.7; >= 4.3.x, < 4.3.18), Snyk (>= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-11040"
      },
      "impact_statement": "CVE-2018-11040 affects Spring Framework 5.0.x prior to 5.0.7 and 4.3.x prior to 4.3.18 due to automatic JSONP support in MappingJackson2JsonView. The target version 5.1.6.RELEASE is NOT affected because all JSONP support was completely removed by upstream vendor (Spring/Pivotal) in commit ac37b678a3 on June 7, 2018, which shipped in Spring Framework 5.1.0.RC1 and all subsequent 5.1.x releases. The vulnerable code (jsonpParameterNames field, AbstractJsonpResponseBodyAdvice class, and all JSONP-related methods) does not exist in this version. This was an upstream fix that predates TuxCare's onboarding of version 5.1.6.RELEASE.\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.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T01:08:46.751659+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 Target repository Spring Framework 5.1.6.RELEASE is not affected by CVE-2018-1199. The vulnerability (path traversal via URL-encoded sequences and improper path normalization) was fixed in upstream Spring Framework versions 4.3.14 and 5.0.3. Version 5.1.6.RELEASE already contains the complete upstream fix authored by Spring developers (rstoyanchev@pivotal.io, jhoeller@pivotal.io) in March 2018,...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 Target repository Spring Framework 5.1.6.RELEASE is not affected by CVE-2018-1199. The vulnerability (path traversal via URL-encoded sequences and improper path normalization) was fixed in upstream Spring Framework versions 4.3.14 and 5.0.3. Version 5.1.6.RELEASE already contains the complete upstream fix authored by Spring developers (rstoyanchev@pivotal.io, jhoeller@pivotal.io) in March 2018,..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-10-30T10:20:00.109102+00:00",
      "status_notes": "Vulnerability CVE-2018-1257 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 The target Spring Framework 5.1.6.RELEASE is not affected by CVE-2018-1257. The fix for this regular expression denial of service vulnerability was included in upstream 5.1.6.RELEASE prior to TuxCare onboarding. The fix commit (ff2228fdaf131d57b5c8c5918ee8d07c6dd9bbac) by Rossen Stoyanchev from Pivotal added the ability to disable the selector header entirely via null-check, preventing maliciou...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1257"
      },
      "impact_statement": "not_affected \u2014 The target Spring Framework 5.1.6.RELEASE is not affected by CVE-2018-1257. The fix for this regular expression denial of service vulnerability was included in upstream 5.1.6.RELEASE prior to TuxCare onboarding. The fix commit (ff2228fdaf131d57b5c8c5918ee8d07c6dd9bbac) by Rossen Stoyanchev from Pivotal added the ability to disable the selector header entirely via null-check, preventing maliciou..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2018-1258 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. CVE-2018-1258 (authorization bypass via proxy method resolution) is not present in Spring Framework 5.1.6.RELEASE. The vulnerability was fixed by upstream commits eaff2c28a7 and aa11721ff0 (authored by jhoeller@pivotal.io on 2018-04-27) which were already included in the upstream 5.1.6.RELEASE released on 2019-03-31. All fix patterns verified present: AopUtils.getMostSpecificMethod correctly processes proxy classes, AnnotationMethodMatcher adds early proxy check, and CacheAspectSupport/ApplicationListenerMethodAdapter properly resolve target methods on proxies.\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 (authorization bypass via proxy method resolution) is not present in Spring Framework 5.1.6.RELEASE. The vulnerability was fixed by upstream commits eaff2c28a7 and aa11721ff0 (authored by jhoeller@pivotal.io on 2018-04-27) which were already included in the upstream 5.1.6.RELEASE released on 2019-03-31. All fix patterns verified present: AopUtils.getMostSpecificMethod correctly processes proxy classes, AnnotationMethodMatcher adds early proxy check, and CacheAspectSupport/ApplicationListenerMethodAdapter properly resolve target methods on proxies.\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.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-10-30T18:55:57.643196+00:00",
      "status_notes": "Vulnerability CVE-2018-1271 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. not_affected \u2014 Spring Framework 5.1.6.RELEASE is not affected by CVE-2018-1271. The vulnerability affected versions prior to 5.0.5 and 4.3.15. The target version 5.1.6.RELEASE (released after 5.0.5) contains the complete upstream fix that was authored by rstoyanchev@pivotal.io and shipped in the upstream release. Both servlet (spring-webmvc) and reactive (spring-webflux) resource handlers include the defense ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1271"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 5.1.6.RELEASE is not affected by CVE-2018-1271. The vulnerability affected versions prior to 5.0.5 and 4.3.15. The target version 5.1.6.RELEASE (released after 5.0.5) contains the complete upstream fix that was authored by rstoyanchev@pivotal.io and shipped in the upstream release. Both servlet (spring-webmvc) and reactive (spring-webflux) resource handlers include the defense ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T12:26:45.505192+00:00",
      "status_notes": "Vulnerability CVE-2018-1272 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. The target Spring Framework 5.1.6.RELEASE is NOT vulnerable to CVE-2018-1272. The vulnerability involved predictable multipart boundary generation using weak Random, allowing attackers to inject malicious multipart sections when servers forward client input. The fix (switching to SecureRandom) was already present in the upstream Spring Framework 5.1.6.RELEASE that TuxCare onboarded, authored by rstoyanchev@pivotal.io. The vulnerable code pattern does not exist in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.15; >= 5.0.0, < 5.0.5), NVD (>= 4.3.0, < 4.3.15; >= 5.0, < 5.0.5), cve.org (< 5.0.5; < 4.3.15), Snyk (>= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; >= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; <= 0).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1272"
      },
      "impact_statement": "The target Spring Framework 5.1.6.RELEASE is NOT vulnerable to CVE-2018-1272. The vulnerability involved predictable multipart boundary generation using weak Random, allowing attackers to inject malicious multipart sections when servers forward client input. The fix (switching to SecureRandom) was already present in the upstream Spring Framework 5.1.6.RELEASE that TuxCare onboarded, authored by rstoyanchev@pivotal.io. The vulnerable code pattern does not exist in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.15; >= 5.0.0, < 5.0.5), NVD (>= 4.3.0, < 4.3.15; >= 5.0, < 5.0.5), cve.org (< 5.0.5; < 4.3.15), Snyk (>= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; >= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; <= 0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T13:42:24.827100+00:00",
      "status_notes": "Vulnerability CVE-2018-15756 does not affect version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core. Target version 5.1.6.RELEASE is not affected by CVE-2018-15756. The vulnerability (DoS via excessive or overlapping HTTP Range headers) was fixed in upstream commit 423aa28ed5 on October 14, 2018, which was included in v5.1.1.RELEASE. The target version 5.1.6.RELEASE (released later in 2019) already contained both required defenses: MAX_RANGES=100 limit (line 48) and sum-of-ranges validation (lines 195-201) in HttpRange.java. The vulnerable code pattern is not present because the fix shipped in the upstream release before TuxCare onboarded version 5.1.6.\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": "Target version 5.1.6.RELEASE is not affected by CVE-2018-15756. The vulnerability (DoS via excessive or overlapping HTTP Range headers) was fixed in upstream commit 423aa28ed5 on October 14, 2018, which was included in v5.1.1.RELEASE. The target version 5.1.6.RELEASE (released later in 2019) already contained both required defenses: MAX_RANGES=100 limit (line 48) and sum-of-ranges validation (lines 195-201) in HttpRange.java. The vulnerable code pattern is not present because the fix shipped in the upstream release before TuxCare onboarded version 5.1.6.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.1.0.RELEASE, < 5.1.1.RELEASE; >= 5.0.0.RELEASE, < 5.0.10.RELEASE; >= 4.2.0.RELEASE, < 4.3.20.RELEASE), NVD (>= 4.2.0, < 4.3.20; >= 5.0.0, < 5.0.10; = 5.1.0), cve.org (= 5.1; >= 5.0.0, <= 5.0.9; >= 4.3, <= 4.3.19), Snyk (>= 4.2.0.RELEASE, < 4.3.20.RELEASE; >= 5.0.0.RELEASE, < 5.0.10.RELEASE; >= 5.1.0.RELEASE, < 5.1.1.RELEASE)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-10-28T22:44:11.275398+00:00",
      "status_notes": "Vulnerability CVE-2021-22060 affects version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2021-22060"
      },
      "action_statement": "Vulnerability CVE-2021-22060 affects version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2021-22096 is fixed in version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2021-22096"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-10T04:24:00.586682+00:00",
      "status_notes": "Vulnerability CVE-2024-22233 does not affect version 5.1.6.RELEASE-tuxcare.4 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 request-URI regex comparison and URI-cache machinery are absent. Handler matching directly queries handler mappings at spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:123, and the class ends with an attribute-ignoring wrapper, with no CachedResult implementation, at spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:212.",
      "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 request-URI regex comparison and URI-cache machinery are absent. Handler matching directly queries handler mappings at spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:123, and the class ends with an attribute-ignoring wrapper, with no CachedResult implementation, at spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:212."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-41249 is fixed in version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2025-41249"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.6.RELEASE-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-41848 is fixed in version 5.1.6.RELEASE-tuxcare.4 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2026-41848"
      }
    }
  ]
}