{
  "@id": "urn:uuid:344ae8d3-5c7a-4d73-b8f9-390b90d1fb70",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 42,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T04:25:00.091559+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T13:10:00.425769+00:00",
      "status_notes": "Vulnerability CVE-2009-1190 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 Spring Framework 5.1.7.RELEASE is not affected by CVE-2009-1190. The vulnerability exists in java.util.regex.Pattern.compile in JDK before version 1.6, where algorithmic complexity in regex compilation with patterns containing multiple optional groups could cause CPU exhaustion. This Spring version requires Java 8 (sourceCompatibility=1.8), making it incompatible with the vulnerable JDK version...",
      "vulnerability": {
        "name": "CVE-2009-1190"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 5.1.7.RELEASE is not affected by CVE-2009-1190. The vulnerability exists in java.util.regex.Pattern.compile in JDK before version 1.6, where algorithmic complexity in regex compilation with patterns containing multiple optional groups could cause CPU exhaustion. This Spring version requires Java 8 (sourceCompatibility=1.8), making it incompatible with the vulnerable JDK version..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-06T17:41:12.900770+00:00",
      "status_notes": "Vulnerability CVE-2011-2730 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. Prechecker: No vulnerable code from the fix was found, and the functions the fix changes were not found in this version. Version 5.1.7.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.7.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.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T09:54:00.051000+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2011-2894 affects Spring Framework 3.0.0-3.0.5 due to unsafe deserialization of proxy classes. The target (Spring Framework 5.1.7.RELEASE) is NOT AFFECTED because the upstream vendor fix was already present when TuxCare onboarded this version. The fix (commit 7d8aa05c40 by jhoeller@vmware.com, July 2011) adds an acceptProxyClasses flag that rejects proxy class deserialization when set to fa...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 CVE-2011-2894 affects Spring Framework 3.0.0-3.0.5 due to unsafe deserialization of proxy classes. The target (Spring Framework 5.1.7.RELEASE) is NOT AFFECTED because the upstream vendor fix was already present when TuxCare onboarded this version. The fix (commit 7d8aa05c40 by jhoeller@vmware.com, July 2011) adds an acceptProxyClasses flag that rejects proxy class deserialization when set to fa..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-02T17:10:00.096270+00:00",
      "status_notes": "Vulnerability CVE-2014-3578 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2014-3578 (directory traversal via crafted URL) is NOT present in target version 5.1.7.RELEASE-tuxcare.2. The vulnerability was fixed by upstream Spring Framework in May 2014 (commit 8ee4651038, issue SPR-11793) and shipped in upstream release 5.1.7.RELEASE in May 2019. TuxCare onboarded this already-fixed version in October 2026. The fix adds validation to StringUtils.cleanPath() that reje...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-3578"
      },
      "impact_statement": "not_affected \u2014 CVE-2014-3578 (directory traversal via crafted URL) is NOT present in target version 5.1.7.RELEASE-tuxcare.2. The vulnerability was fixed by upstream Spring Framework in May 2014 (commit 8ee4651038, issue SPR-11793) and shipped in upstream release 5.1.7.RELEASE in May 2019. TuxCare onboarded this already-fixed version in October 2026. The fix adds validation to StringUtils.cleanPath() that reje..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T19:20:00.402348+00:00",
      "status_notes": "Vulnerability CVE-2015-0201 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5 where the SockJS client used AlternativeJdkIdGenerator for session IDs, which employed a predictable java.util.Random after initial seeding. The target version 5.1.7.RELEASE uses the fixed JdkIdGenerator implementation (which uses UUID.randomUUID() with SecureRandom) that was introduced in commit 52b8f34468 (Jan 2015). This fix was alrea...",
      "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 for session IDs, which employed a predictable java.util.Random after initial seeding. The target version 5.1.7.RELEASE uses the fixed JdkIdGenerator implementation (which uses UUID.randomUUID() with SecureRandom) that was introduced in commit 52b8f34468 (Jan 2015). This fix was alrea..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:13:11.896857+00:00",
      "status_notes": "Vulnerability CVE-2015-5211 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. Spring Framework 5.1.7.RELEASE is not affected by CVE-2015-5211 (Reflected File Download attack). The RFD protection mechanism was added by upstream Spring developers in October 2015 (commit 2bd1daa75ee) and was already present in Spring Framework 5.0.0 and all subsequent releases, including 5.1.7.RELEASE. The addContentDispositionHeader method in AbstractMessageConverterMethodProcessor checks URL file extensions and adds Content-Disposition headers with safe filenames when non-whitelisted extensions are detected, preventing RFD exploits. This is an upstream fix that shipped in the release before TuxCare onboarded it.\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.7.RELEASE is not affected by CVE-2015-5211 (Reflected File Download attack). The RFD protection mechanism was added by upstream Spring developers in October 2015 (commit 2bd1daa75ee) and was already present in Spring Framework 5.0.0 and all subsequent releases, including 5.1.7.RELEASE. The addContentDispositionHeader method in AbstractMessageConverterMethodProcessor checks URL file extensions and adds Content-Disposition headers with safe filenames when non-whitelisted extensions are detected, preventing RFD exploits. This is an upstream fix that shipped in the release before TuxCare onboarded it.\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.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:20:11.775734+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. CVE-2016-5007 is NOT present in Spring Framework 5.1.7.RELEASE. The upstream fix (SPR-14321) introducing the HandlerMapping introspection API was already included in the upstream 5.1.7.RELEASE before TuxCare onboarding. The fix provides MatchableHandlerMapping interface to ensure Spring Security and Spring MVC use identical pattern matching logic, eliminating authorization bypass vulnerabilities from pattern matching discrepancies. The target contains all fix components: MatchableHandlerMapping interface, HandlerMappingIntrospector helper, RequestMatchResult class, and both AbstractUrlHandlerMapping and RequestMappingHandlerMapping correctly implement the interface. Fix authored by upstream Spring team (Rossen Stoyanchev, rstoyanchev@pivotal.io), not TuxCare.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.1), NVD (= 3.2.0; = 4.0.0; = 4.1.0; = 4.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 3.2.15; = 3.2.16; = 3.2.17; = 3.2.18; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.1.8; = 4.1.9; = 4.2.1; = 4.2.2; = 4.2.3; = 4.2.4; = 4.2.5; = 4.2.6; = 4.2.7; = 4.2.8; = 4.2.9), cve.org (>= 3.2, < 3.3; >= 4.0, < 4.1; >= 4.1, < 4.2; >= 4.2, < 4.3; < 3.2), Snyk (>= 3.2.0.RELEASE, < 4.3.1.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-5007"
      },
      "impact_statement": "CVE-2016-5007 is NOT present in Spring Framework 5.1.7.RELEASE. The upstream fix (SPR-14321) introducing the HandlerMapping introspection API was already included in the upstream 5.1.7.RELEASE before TuxCare onboarding. The fix provides MatchableHandlerMapping interface to ensure Spring Security and Spring MVC use identical pattern matching logic, eliminating authorization bypass vulnerabilities from pattern matching discrepancies. The target contains all fix components: MatchableHandlerMapping interface, HandlerMappingIntrospector helper, RequestMatchResult class, and both AbstractUrlHandlerMapping and RequestMappingHandlerMapping correctly implement the interface. Fix authored by upstream Spring team (Rossen Stoyanchev, rstoyanchev@pivotal.io), not TuxCare.\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.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T14:01:13.058306+00:00",
      "status_notes": "Vulnerability CVE-2018-11040 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. CVE-2018-11040 does not affect Spring Framework 5.1.7.RELEASE. The vulnerability involved automatic JSONP support being enabled by default through query parameters \"jsonp\" and \"callback\" in MappingJackson2JsonView and AbstractJsonpResponseBodyAdvice. This entire JSONP feature was completely removed from Spring Framework 5.1 in upstream commit ac37b678a3 (June 7, 2018) by Sebastien Deleuze, before version 5.1.7.RELEASE was created. The target repository contains no JSONP handling code - the vulnerable jsonpParameterNames field, JSONP wrapping methods, and AbstractJsonpResponseBodyAdvice class have all been deleted. TuxCare onboarded version 5.1.7.RELEASE which already included this upstream fix.\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 does not affect Spring Framework 5.1.7.RELEASE. The vulnerability involved automatic JSONP support being enabled by default through query parameters \"jsonp\" and \"callback\" in MappingJackson2JsonView and AbstractJsonpResponseBodyAdvice. This entire JSONP feature was completely removed from Spring Framework 5.1 in upstream commit ac37b678a3 (June 7, 2018) by Sebastien Deleuze, before version 5.1.7.RELEASE was created. The target repository contains no JSONP handling code - the vulnerable jsonpParameterNames field, JSONP wrapping methods, and AbstractJsonpResponseBodyAdvice class have all been deleted. TuxCare onboarded version 5.1.7.RELEASE which already included this upstream fix.\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.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T01:15:16.880365+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 The target Spring Framework 5.1.7.RELEASE is NOT AFFECTED by CVE-2018-1199. The vulnerability involved path traversal via special character encodings (backslashes, percent-encoded dots, duplicate slashes) to access files outside configured static resource locations. The upstream fix (SPR-16616, commits 0e28bee0f1, 91b803a231, f59ea610df, 13356a7ee2, b9ebdaaf37, f046a066ec) was already present i...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 The target Spring Framework 5.1.7.RELEASE is NOT AFFECTED by CVE-2018-1199. The vulnerability involved path traversal via special character encodings (backslashes, percent-encoded dots, duplicate slashes) to access files outside configured static resource locations. The upstream fix (SPR-16616, commits 0e28bee0f1, 91b803a231, f59ea610df, 13356a7ee2, b9ebdaaf37, f046a066ec) was already present i..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T10:20:00.109102+00:00",
      "status_notes": "Vulnerability CVE-2018-1257 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 The target Spring Framework 5.1.7.RELEASE is NOT affected by CVE-2018-1257. The vulnerability involves a regex denial of service attack via malicious selector headers in STOMP subscription messages. The upstream vendor (Spring/Pivotal) fixed this vulnerability in commit ff2228fdaf (April 2018) by adding a null-check guard that prevents parsing of selector expressions when selector support is di...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1257"
      },
      "impact_statement": "not_affected \u2014 The target Spring Framework 5.1.7.RELEASE is NOT affected by CVE-2018-1257. The vulnerability involves a regex denial of service attack via malicious selector headers in STOMP subscription messages. The upstream vendor (Spring/Pivotal) fixed this vulnerability in commit ff2228fdaf (April 2018) by adding a null-check guard that prevents parsing of selector expressions when selector support is di..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2018-1258 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. The target repository (Spring Framework 5.1.7.RELEASE) is NOT AFFECTED by CVE-2018-1258. The vulnerability, which caused authorization bypass in method security due to incorrect method resolution on proxy objects, was fixed by upstream Spring developers in commit aa11721ff0 (2018-04-27). This fix was already included in the upstream v5.1.7.RELEASE tag (2019-05-09) that TuxCare onboarded. All three critical files (AopUtils.java, CacheAspectSupport.java, ApplicationListenerMethodAdapter.java, AnnotationMethodMatcher.java) contain the correct proxy-handling logic that prevents security annotations from being missed during authorization checks.\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": "The target repository (Spring Framework 5.1.7.RELEASE) is NOT AFFECTED by CVE-2018-1258. The vulnerability, which caused authorization bypass in method security due to incorrect method resolution on proxy objects, was fixed by upstream Spring developers in commit aa11721ff0 (2018-04-27). This fix was already included in the upstream v5.1.7.RELEASE tag (2019-05-09) that TuxCare onboarded. All three critical files (AopUtils.java, CacheAspectSupport.java, ApplicationListenerMethodAdapter.java, AnnotationMethodMatcher.java) contain the correct proxy-handling logic that prevents security annotations from being missed during authorization checks.\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.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T19:17:00.109182+00:00",
      "status_notes": "Vulnerability CVE-2018-1271 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1271 is NOT present in Spring Framework 5.1.7.RELEASE. The vulnerability affects versions 5.0 prior to 5.0.5 and 4.3 prior to 4.3.15. The target version (5.1.7.RELEASE) was released in May 2019, well after the fix was committed to upstream in March 2018. All three defense mechanisms from the security patches are present in the target: (1) backslash-to-forward-slash normalization, (2) d...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1271"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1271 is NOT present in Spring Framework 5.1.7.RELEASE. The vulnerability affects versions 5.0 prior to 5.0.5 and 4.3 prior to 4.3.15. The target version (5.1.7.RELEASE) was released in May 2019, well after the fix was committed to upstream in March 2018. All three defense mechanisms from the security patches are present in the target: (1) backslash-to-forward-slash normalization, (2) d..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T12:38:41.778029+00:00",
      "status_notes": "Vulnerability CVE-2018-1272 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. CVE-2018-1272 addresses predictable multipart boundary generation in Spring Framework that could allow attackers to inject additional parts into proxied multipart requests. The vulnerability existed when Random (pseudorandom) was used instead of SecureRandom for boundary generation. The target version 5.1.7.RELEASE is NOT affected because the upstream Spring Framework fix (commit 847202c8) was already included in the 5.1.7.RELEASE that TuxCare onboarded. The vulnerable pattern (using insecure Random) is not present in the target codebase. The fix was authored by upstream Spring/Pivotal developers (jhoeller@pivotal.io), not by TuxCare.\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": "CVE-2018-1272 addresses predictable multipart boundary generation in Spring Framework that could allow attackers to inject additional parts into proxied multipart requests. The vulnerability existed when Random (pseudorandom) was used instead of SecureRandom for boundary generation. The target version 5.1.7.RELEASE is NOT affected because the upstream Spring Framework fix (commit 847202c8) was already included in the 5.1.7.RELEASE that TuxCare onboarded. The vulnerable pattern (using insecure Random) is not present in the target codebase. The fix was authored by upstream Spring/Pivotal developers (jhoeller@pivotal.io), not by TuxCare.\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.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:46:23.146908+00:00",
      "status_notes": "Vulnerability CVE-2018-15756 does not affect version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core. CVE-2018-15756 fix was already present in upstream Spring Framework 5.1.7.RELEASE when it was originally released on October 3, 2018. The fix (commit 423aa28ed5 by rstoyanchev@pivotal.io) limits HTTP Range requests to 100 ranges maximum and validates that the sum of all requested ranges is less than the resource length, preventing the DoS vulnerability. TuxCare onboarded this version with the fix already included, so the target is not vulnerable.\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 fix was already present in upstream Spring Framework 5.1.7.RELEASE when it was originally released on October 3, 2018. The fix (commit 423aa28ed5 by rstoyanchev@pivotal.io) limits HTTP Range requests to 100 ranges maximum and validates that the sum of all requested ranges is less than the resource length, preventing the DoS vulnerability. TuxCare onboarded this version with the fix already included, so the target is not vulnerable.\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.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-28T22:44:11.275398+00:00",
      "status_notes": "Vulnerability CVE-2021-22060 affects version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2021-22060"
      },
      "action_statement": "Vulnerability CVE-2021-22060 affects version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-27T12:49:56.768090+00:00",
      "status_notes": "Vulnerability CVE-2021-22096 is fixed in version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2021-22096"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-10T04:25:00.091559+00:00",
      "status_notes": "Vulnerability CVE-2024-22233 does not affect version 5.1.7.RELEASE-tuxcare.2 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 regular expression comparison is absent. In spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:123, matching directly wraps the request and iterates handler mappings; the class has no CachedResult, cache filter, or cached-URI regex comparison, and its sole nested class only suppresses attribute writes (spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:212).",
      "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 regular expression comparison is absent. In spring-webmvc/src/main/java/org/springframework/web/servlet/handler/HandlerMappingIntrospector.java:123, matching directly wraps the request and iterates handler mappings; the class has no CachedResult, cache filter, or cached-URI regex comparison, and its sole nested class only suppresses attribute writes (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.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-27T12:49:56.768090+00:00",
      "status_notes": "Vulnerability CVE-2025-41249 is fixed in version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2025-41249"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.7.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-27T12:49:56.768090+00:00",
      "status_notes": "Vulnerability CVE-2026-41848 is fixed in version 5.1.7.RELEASE-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2026-41848"
      }
    }
  ]
}