{
  "@id": "urn:uuid:bf2d5d47-1cc0-43e4-b881-47a0d000c373",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-09T08:54:13.387516+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2009-1190 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. not_affected \u2014 Spring Framework 5.1.19.RELEASE is not affected by CVE-2009-1190. The vulnerability requires JDK before 1.6 (where Pattern.compile has algorithmic complexity issues) combined with Spring Framework 1.1.0-2.5.6 or 3.0.0.M1-M2. The target requires JDK 8+ (sourceCompatibility=1.8), which fixed the underlying regex engine vulnerability ~8 years before Spring 5.1.19 was released. While RemoteInvocati...",
      "vulnerability": {
        "name": "CVE-2009-1190"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 5.1.19.RELEASE is not affected by CVE-2009-1190. The vulnerability requires JDK before 1.6 (where Pattern.compile has algorithmic complexity issues) combined with Spring Framework 1.1.0-2.5.6 or 3.0.0.M1-M2. The target requires JDK 8+ (sourceCompatibility=1.8), which fixed the underlying regex engine vulnerability ~8 years before Spring 5.1.19 was released. While RemoteInvocati..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2011-2730 does not affect version 5.1.19.RELEASE-tuxcare.5 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.19.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.19.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.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. not_affected \u2014 CVE-2011-2894 is not present in Spring Framework 5.1.19.RELEASE. The upstream fix (commit 7d8aa05c by Juergen Hoeller, July 2011) added an acceptProxyClasses mechanism to ConfigurableObjectInputStream, RemoteInvocationSerializingExporter, and CodebaseAwareObjectInputStream. This fix shipped with the upstream release before TuxCare's onboarding commit (d8956144), making the vulnerable pattern (u...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 CVE-2011-2894 is not present in Spring Framework 5.1.19.RELEASE. The upstream fix (commit 7d8aa05c by Juergen Hoeller, July 2011) added an acceptProxyClasses mechanism to ConfigurableObjectInputStream, RemoteInvocationSerializingExporter, and CodebaseAwareObjectInputStream. This fix shipped with the upstream release before TuxCare's onboarding commit (d8956144), making the vulnerable pattern (u..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2014-3578 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. not_affected \u2014 CVE-2014-3578 directory traversal vulnerability is NOT present in Spring Framework 5.1.19.RELEASE. The vulnerability affected versions 3.x before 3.2.9 and 4.0 before 4.0.5. The fix (commit 8ee465103850a) was applied by upstream Spring Framework on May 15, 2014, and was already present in the upstream 5.1.19.RELEASE when TuxCare onboarded it. The fix validates URI scheme prefixes to prevent pse...",
      "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.1.19.RELEASE. The vulnerability affected versions 3.x before 3.2.9 and 4.0 before 4.0.5. The fix (commit 8ee465103850a) was applied by upstream Spring Framework on May 15, 2014, and was already present in the upstream 5.1.19.RELEASE when TuxCare onboarded it. The fix validates URI scheme prefixes to prevent pse..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2015-0201 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. not_affected \u2014 Spring Framework 5.1.19.RELEASE is not affected by CVE-2015-0201. This CVE affected versions 4.1.x before 4.1.5 where the Java SockJS client generated predictable session IDs using AlternativeJdkIdGenerator (which uses SecureRandom only for initial seed, then predictable java.util.Random). The fix, introduced in version 4.1.5 by upstream Pivotal, switched to JdkIdGenerator which uses cryptograp...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-0201"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 5.1.19.RELEASE is not affected by CVE-2015-0201. This CVE affected versions 4.1.x before 4.1.5 where the Java SockJS client generated predictable session IDs using AlternativeJdkIdGenerator (which uses SecureRandom only for initial seed, then predictable java.util.Random). The fix, introduced in version 4.1.5 by upstream Pivotal, switched to JdkIdGenerator which uses cryptograp..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2015-5211 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. CVE-2015-5211 (Reflected File Download/RFD attack) is NOT present in Spring Framework 5.1.19.RELEASE. The upstream fix (commit 2bd1daa75e by rstoyanchev@pivotal.io, 2015-10-04) was already included in the v5.1.19.RELEASE tag before TuxCare onboarded this version. All three RFD defenses are present: (1) URL filename extraction strips query/fragment/path parameters via UriUtils.extractFileExtension(), (2) JSONP support was completely removed in 2018 (eliminating the batch script attack vector), and (3) JAF-based MIME type resolution is controlled. The vulnerable code pattern described in the CVE does not exist in this version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.2.0, < 4.2.2; >= 4.0.0, < 4.1.8; < 3.2.15), NVD (= 3.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.0; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.2.0; = 4.2.1), Snyk (>= 3.2.0.RELEASE, < 3.2.15.RELEASE; >= 4.0.0.RELEASE, < 4.1.8.RELEASE; >= 4.2.0.RELEASE, < 4.2.2.RELEASE; <= 0; <= 0).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-5211"
      },
      "impact_statement": "CVE-2015-5211 (Reflected File Download/RFD attack) is NOT present in Spring Framework 5.1.19.RELEASE. The upstream fix (commit 2bd1daa75e by rstoyanchev@pivotal.io, 2015-10-04) was already included in the v5.1.19.RELEASE tag before TuxCare onboarded this version. All three RFD defenses are present: (1) URL filename extraction strips query/fragment/path parameters via UriUtils.extractFileExtension(), (2) JSONP support was completely removed in 2018 (eliminating the batch script attack vector), and (3) JAF-based MIME type resolution is controlled. The vulnerable code pattern described in the CVE does not exist in this version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.2.0, < 4.2.2; >= 4.0.0, < 4.1.8; < 3.2.15), NVD (= 3.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.0; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.2.0; = 4.2.1), Snyk (>= 3.2.0.RELEASE, < 3.2.15.RELEASE; >= 4.0.0.RELEASE, < 4.1.8.RELEASE; >= 4.2.0.RELEASE, < 4.2.2.RELEASE; <= 0; <= 0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. CVE-2016-5007 is NOT present in Spring Framework 5.1.19.RELEASE. The fix (MatchableHandlerMapping introspection API) was already included in the upstream release when TuxCare onboarded it. Commit a30ab30e4e by rstoyanchev@pivotal.io introduced the unified pattern-matching API that prevents authorization bypass vulnerabilities caused by mismatches between Spring Security's pattern matching and Spring MVC's routing logic. All fix components are present: MatchableHandlerMapping interface, RequestMatchResult class, HandlerMappingIntrospector helper, and match() methods in both AbstractUrlHandlerMapping (line 294) and RequestMappingHandlerMapping (line 337).\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.19.RELEASE. The fix (MatchableHandlerMapping introspection API) was already included in the upstream release when TuxCare onboarded it. Commit a30ab30e4e by rstoyanchev@pivotal.io introduced the unified pattern-matching API that prevents authorization bypass vulnerabilities caused by mismatches between Spring Security's pattern matching and Spring MVC's routing logic. All fix components are present: MatchableHandlerMapping interface, RequestMatchResult class, HandlerMappingIntrospector helper, and match() methods in both AbstractUrlHandlerMapping (line 294) and RequestMappingHandlerMapping (line 337).\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.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2018-11040 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. Spring Framework 5.1.19.RELEASE is not affected by CVE-2018-11040. The vulnerable JSONP functionality was completely removed by upstream Spring Framework developers before the 5.1.0.RC1 release. Commit ac37b678a3 (authored by sdeleuze@pivotal.io on 2018-06-07) removed all JSONP support code, including MappingJackson2JsonView's jsonpParameterNames field and related methods, AbstractJsonpResponseBodyAdvice class, and JsonpPollingTransportHandler/JsonpReceivingTransportHandler classes. This removal commit is an ancestor of the target version's HEAD and was included in the upstream 5.1.19.RELEASE that TuxCare onboarded. Code verification confirms no JSONP functionality exists in the target: MappingJackson2JsonView contains only 177 lines with no JSONP parameter handling, and JSONP-related classes are absent from the codebase.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE), NVD (< 4.3.18; >= 5.0.0, < 5.0.7), cve.org (>= 5.0.x, < 5.0.7; >= 4.3.x, < 4.3.18), Snyk (>= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-11040"
      },
      "impact_statement": "Spring Framework 5.1.19.RELEASE is not affected by CVE-2018-11040. The vulnerable JSONP functionality was completely removed by upstream Spring Framework developers before the 5.1.0.RC1 release. Commit ac37b678a3 (authored by sdeleuze@pivotal.io on 2018-06-07) removed all JSONP support code, including MappingJackson2JsonView's jsonpParameterNames field and related methods, AbstractJsonpResponseBodyAdvice class, and JsonpPollingTransportHandler/JsonpReceivingTransportHandler classes. This removal commit is an ancestor of the target version's HEAD and was included in the upstream 5.1.19.RELEASE that TuxCare onboarded. Code verification confirms no JSONP functionality exists in the target: MappingJackson2JsonView contains only 177 lines with no JSONP parameter handling, and JSONP-related classes are absent from the codebase.\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.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1199 affects Spring Framework versions before 4.3.14 and 5.0.x before 5.0.3. The vulnerability allows attackers to bypass security constraints by using URL paths with special encodings (percent-encoded traversal sequences like %2E%2E%2F), duplicate slashes, or backslashes to access protected static resources.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1199 affects Spring Framework versions before 4.3.14 and 5.0.x before 5.0.3. The vulnerability allows attackers to bypass security constraints by using URL paths with special encodings (percent-encoded traversal sequences like %2E%2E%2F), duplicate slashes, or backslashes to access protected static resources."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2018-1257 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1257 is NOT present in Spring Framework 5.1.19.RELEASE. The vulnerability affected versions 5.0.x prior to 5.0.6 and 4.3.x prior to 4.3.17. The fix was introduced upstream in April 2018 and included in Spring Framework 5.1.0.RC1 (and all subsequent 5.1.x releases). The target version 5.1.19.RELEASE contains the complete upstream fix: the selector header name can be set to null to disab...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1257"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1257 is NOT present in Spring Framework 5.1.19.RELEASE. The vulnerability affected versions 5.0.x prior to 5.0.6 and 4.3.x prior to 4.3.17. The fix was introduced upstream in April 2018 and included in Spring Framework 5.1.0.RC1 (and all subsequent 5.1.x releases). The target version 5.1.19.RELEASE contains the complete upstream fix: the selector header name can be set to null to disab..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2018-1258 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. CVE-2018-1258 affects Spring Framework 5.0.5 when used with Spring Security, causing an authorization bypass when method security annotations are not properly resolved on JDK dynamic proxies. The target repository (Spring Framework 5.1.19.RELEASE) is NOT affected because the fix was already included in the upstream Spring Framework 5.1.0 release (April 2018) via commits eaff2c28a7 and aa11721ff0, authored by upstream developer Juergen Hoeller. When TuxCare onboarded version 5.1.19.RELEASE, the complete fix was already present. All three key fix components are verified in the target: AopUtils.getMostSpecificMethod correctly handles proxy classes, CacheAspectSupport properly resolves target methods for annotation lookup, and AnnotationMethodMatcher includes the proxy class early-return logic.\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 affects Spring Framework 5.0.5 when used with Spring Security, causing an authorization bypass when method security annotations are not properly resolved on JDK dynamic proxies. The target repository (Spring Framework 5.1.19.RELEASE) is NOT affected because the fix was already included in the upstream Spring Framework 5.1.0 release (April 2018) via commits eaff2c28a7 and aa11721ff0, authored by upstream developer Juergen Hoeller. When TuxCare onboarded version 5.1.19.RELEASE, the complete fix was already present. All three key fix components are verified in the target: AopUtils.getMostSpecificMethod correctly handles proxy classes, CacheAspectSupport properly resolves target methods for annotation lookup, and AnnotationMethodMatcher includes the proxy class early-return logic.\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.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2018-1271 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1271 directory traversal vulnerability is NOT present in Spring Framework 5.1.19.RELEASE. The upstream fix commits (SPR-16616) that add URL-decoded path validation and backslash normalization were already included in the Spring Framework 5.1.19.RELEASE that TuxCare onboarded. The fix code is comprehensively present in both webmvc and webflux modules, implementing defense-in-depth with ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1271"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1271 directory traversal vulnerability is NOT present in Spring Framework 5.1.19.RELEASE. The upstream fix commits (SPR-16616) that add URL-decoded path validation and backslash normalization were already included in the Spring Framework 5.1.19.RELEASE that TuxCare onboarded. The fix code is comprehensively present in both webmvc and webflux modules, implementing defense-in-depth with ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2018-1272 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. The target Spring Framework 5.1.19.RELEASE is not affected by CVE-2018-1272. The vulnerability required predictable multipart boundary generation using insecure Random, but the target uses SecureRandom for all boundary generation (MimeTypeUtils.java:364). The fix commit ab2410c754b67902f002bfcc0c3895bd7772d39f was applied by upstream author Rossen Stoyanchev on 2018-03-23, more than 2 years before Spring Framework 5.1.19.RELEASE was released (2020-10-27). The fix was already included in the upstream release that TuxCare onboarded.\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.19.RELEASE is not affected by CVE-2018-1272. The vulnerability required predictable multipart boundary generation using insecure Random, but the target uses SecureRandom for all boundary generation (MimeTypeUtils.java:364). The fix commit ab2410c754b67902f002bfcc0c3895bd7772d39f was applied by upstream author Rossen Stoyanchev on 2018-03-23, more than 2 years before Spring Framework 5.1.19.RELEASE was released (2020-10-27). The fix was already included in the upstream release that TuxCare onboarded.\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.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2018-15756 does not affect version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core. The target Spring Framework 5.1.19.RELEASE is NOT affected by CVE-2018-15756. The vulnerability fix (MAX_RANGES limit and range sum validation) was already present in the upstream Spring Framework 5.1.19.RELEASE before TuxCare onboarded it. The fix was authored by Rossen Stoyanchev (rstoyanchev@pivotal.io) in commit 423aa28ed5 on 2018-10-03, addressing SPR-17318. The vulnerable code pattern does not exist in the target.\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.1.19.RELEASE is NOT affected by CVE-2018-15756. The vulnerability fix (MAX_RANGES limit and range sum validation) was already present in the upstream Spring Framework 5.1.19.RELEASE before TuxCare onboarded it. The fix was authored by Rossen Stoyanchev (rstoyanchev@pivotal.io) in commit 423aa28ed5 on 2018-10-03, addressing SPR-17318. The vulnerable code pattern does not exist in the target.\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.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2021-22060 affects version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2021-22060"
      },
      "action_statement": "Vulnerability CVE-2021-22060 affects version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2021-22096 is fixed in version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2021-22096"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2024-22233 affects version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2024-22233"
      },
      "action_statement": "Vulnerability CVE-2024-22233 affects version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2025-41249 affects version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2025-41249"
      },
      "action_statement": "Vulnerability CVE-2025-41249 affects version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.1.19.RELEASE-tuxcare.5"
          }
        }
      ],
      "timestamp": "2026-11-09T08:54:13.387516+00:00",
      "status_notes": "Vulnerability CVE-2026-41848 is fixed in version 5.1.19.RELEASE-tuxcare.5 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2026-41848"
      }
    }
  ]
}