{
  "@id": "urn:uuid:2a46b2bf-39a6-4ebf-9d04-a30b4e90e46d",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 52,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-06T17:28:28.319057+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T12:02:22.275588+00:00",
      "status_notes": "Vulnerability CVE-2009-1190 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2009-1190 is fundamentally a JDK vulnerability affecting Pattern.compile in JDK versions before 1.6, which could be triggered through Spring Framework's data binding mechanisms. While Spring 5.2.11 contains code paths that compile regex patterns without validation (PatternEditor.setAsText(), JdkRegexpMethodPointcut.compilePatterns()), these paths execute in a JDK 8+ runtime environment wher...",
      "vulnerability": {
        "name": "CVE-2009-1190"
      },
      "impact_statement": "not_affected \u2014 CVE-2009-1190 is fundamentally a JDK vulnerability affecting Pattern.compile in JDK versions before 1.6, which could be triggered through Spring Framework's data binding mechanisms. While Spring 5.2.11 contains code paths that compile regex patterns without validation (PatternEditor.setAsText(), JdkRegexpMethodPointcut.compilePatterns()), these paths execute in a JDK 8+ runtime environment wher..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-06T17:28:28.319057+00:00",
      "status_notes": "Vulnerability CVE-2011-2730 does not affect version 5.2.11.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.2.11.RELEASE is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-wv88-pf73-x22p (affected up to 3.0.6), NVD (affected up to 3.0.5), Snyk (affected up to 3.0.6).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2730"
      },
      "impact_statement": "Prechecker: No vulnerable code from the fix was found, and the functions the fix changes were not found in this version. Version 5.2.11.RELEASE is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-wv88-pf73-x22p (affected up to 3.0.6), NVD (affected up to 3.0.5), Snyk (affected up to 3.0.6)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T09:33:05.210640+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2011-2894 deserialization vulnerability is not affecting Spring Framework 5.2.11.RELEASE-tuxcare.3. The upstream vendor fix (commit 7d8aa05c407 by jhoeller@vmware.com, July 2011) was already present in the upstream release that TuxCare onboarded. The fix adds an acceptProxyClasses flag that can reject deserialization of proxy classes, preventing arbitrary code execution through malicious In...",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 CVE-2011-2894 deserialization vulnerability is not affecting Spring Framework 5.2.11.RELEASE-tuxcare.3. The upstream vendor fix (commit 7d8aa05c407 by jhoeller@vmware.com, July 2011) was already present in the upstream release that TuxCare onboarded. The fix adds an acceptProxyClasses flag that can reject deserialization of proxy classes, preventing arbitrary code execution through malicious In..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-02T16:42:00.216861+00:00",
      "status_notes": "Vulnerability CVE-2014-3578 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 The target Spring Framework 5.2.11.RELEASE is not affected by CVE-2014-3578. The fix for this directory traversal vulnerability was already present in the upstream release 5.2.11.RELEASE when TuxCare onboarded it. The upstream fix (commit 8ee465103850a3dca018273fe5952e40d5c45a66 from May 15, 2014, authored by Rossen Stoyanchev) adds validation to the StringUtils.cleanPath method that prevents d...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-3578"
      },
      "impact_statement": "not_affected \u2014 The target Spring Framework 5.2.11.RELEASE is not affected by CVE-2014-3578. The fix for this directory traversal vulnerability was already present in the upstream release 5.2.11.RELEASE when TuxCare onboarded it. The upstream fix (commit 8ee465103850a3dca018273fe5952e40d5c45a66 from May 15, 2014, authored by Rossen Stoyanchev) adds validation to the StringUtils.cleanPath method that prevents d..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T19:05:00.096825+00:00",
      "status_notes": "Vulnerability CVE-2015-0201 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5 due to predictable session ID generation in the Java SockJS client. The vulnerability was fixed in 4.1.5 (January 2015) by switching from AlternativeJdkIdGenerator (which uses predictable java.util.Random after initial SecureRandom seed) to JdkIdGenerator (which uses cryptographically secure UUID.randomUUID() for each generation). The ta...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-0201"
      },
      "impact_statement": "not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5 due to predictable session ID generation in the Java SockJS client. The vulnerability was fixed in 4.1.5 (January 2015) by switching from AlternativeJdkIdGenerator (which uses predictable java.util.Random after initial SecureRandom seed) to JdkIdGenerator (which uses cryptographically secure UUID.randomUUID() for each generation). The ta..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T12:53:41.382779+00:00",
      "status_notes": "Vulnerability CVE-2015-5211 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. CVE-2015-5211 RFD (Reflected File Download) vulnerability is not present in Spring Framework 5.2.11.RELEASE. The upstream fix (commit 2bd1daa75e by rstoyanchev@pivotal.io) was already included in v5.2.11.RELEASE before TuxCare onboarding. The defensive code includes: (1) Content-Disposition header with safe filename for non-whitelisted extensions in AbstractMessageConverterMethodProcessor, (2) SAFE_EXTENSIONS whitelist checking, and (3) SockJS path validation rejecting semicolons in filenames.\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 RFD (Reflected File Download) vulnerability is not present in Spring Framework 5.2.11.RELEASE. The upstream fix (commit 2bd1daa75e by rstoyanchev@pivotal.io) was already included in v5.2.11.RELEASE before TuxCare onboarding. The defensive code includes: (1) Content-Disposition header with safe filename for non-whitelisted extensions in AbstractMessageConverterMethodProcessor, (2) SAFE_EXTENSIONS whitelist checking, and (3) SockJS path validation rejecting semicolons in filenames.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.2.0, < 4.2.2; >= 4.0.0, < 4.1.8; < 3.2.15), NVD (= 3.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.0; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.2.0; = 4.2.1), Snyk (>= 3.2.0.RELEASE, < 3.2.15.RELEASE; >= 4.0.0.RELEASE, < 4.1.8.RELEASE; >= 4.2.0.RELEASE, < 4.2.2.RELEASE; <= 0; <= 0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:06:45.482707+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. CVE-2016-5007 is not present in Spring Framework 5.2.11.RELEASE. The upstream vendor (Pivotal/VMware/Spring) fixed this vulnerability in commit a30ab30e4e (SPR-14321) by introducing the HandlerMappingIntrospector API with MatchableHandlerMapping interface. This fix was first released in Spring Framework 4.3.1 and is present in all 5.2.x releases including 5.2.11.RELEASE. The target contains the complete fix: MatchableHandlerMapping interface, HandlerMappingIntrospector class, and match() method implementations in both AbstractUrlHandlerMapping and RequestMappingHandlerMapping.\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.2.11.RELEASE. The upstream vendor (Pivotal/VMware/Spring) fixed this vulnerability in commit a30ab30e4e (SPR-14321) by introducing the HandlerMappingIntrospector API with MatchableHandlerMapping interface. This fix was first released in Spring Framework 4.3.1 and is present in all 5.2.x releases including 5.2.11.RELEASE. The target contains the complete fix: MatchableHandlerMapping interface, HandlerMappingIntrospector class, and match() method implementations in both AbstractUrlHandlerMapping and RequestMappingHandlerMapping.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.1), NVD (= 3.2.0; = 4.0.0; = 4.1.0; = 4.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 3.2.15; = 3.2.16; = 3.2.17; = 3.2.18; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.1.8; = 4.1.9; = 4.2.1; = 4.2.2; = 4.2.3; = 4.2.4; = 4.2.5; = 4.2.6; = 4.2.7; = 4.2.8; = 4.2.9), cve.org (>= 3.2, < 3.3; >= 4.0, < 4.1; >= 4.1, < 4.2; >= 4.2, < 4.3; < 3.2), Snyk (>= 3.2.0.RELEASE, < 4.3.1.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:49:07.796693+00:00",
      "status_notes": "Vulnerability CVE-2018-11040 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. Spring Framework 5.2.11.RELEASE is not affected by CVE-2018-11040. The vulnerable JSONP (JSON with Padding) code was completely removed from the upstream Spring Framework codebase in version 5.1.0.RC1 (June 2018, commit ac37b678a3), well before version 5.2.11.RELEASE was released (October 2020). The fix was authored by upstream Spring developer Sebastien Deleuze and shipped in the upstream release that TuxCare later onboarded. No JSONP-related code exists in the target repository.\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.2.11.RELEASE is not affected by CVE-2018-11040. The vulnerable JSONP (JSON with Padding) code was completely removed from the upstream Spring Framework codebase in version 5.1.0.RC1 (June 2018, commit ac37b678a3), well before version 5.2.11.RELEASE was released (October 2020). The fix was authored by upstream Spring developer Sebastien Deleuze and shipped in the upstream release that TuxCare later onboarded. No JSONP-related code exists in the target repository.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE), NVD (< 4.3.18; >= 5.0.0, < 5.0.7), cve.org (>= 5.0.x, < 5.0.7; >= 4.3.x, < 4.3.18), Snyk (>= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE; >= 4.3.0.RELEASE, < 4.3.18.RELEASE; >= 5.0.0.RELEASE, < 5.0.7.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T00:50:55.977171+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1199 fix was already present in upstream Spring Framework 5.2.11.RELEASE before TuxCare onboarded this version. The vulnerability allowed bypassing security constraints via path parameters with special encodings (duplicate slashes, backslashes, URL-encoded traversal sequences). The fix (commit 0e28bee0f1) adds path normalization (backslash\u2192forward slash conversion, duplicate slash remo...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1199 fix was already present in upstream Spring Framework 5.2.11.RELEASE before TuxCare onboarded this version. The vulnerability allowed bypassing security constraints via path parameters with special encodings (duplicate slashes, backslashes, URL-encoded traversal sequences). The fix (commit 0e28bee0f1) adds path normalization (backslash\u2192forward slash conversion, duplicate slash remo..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T08:55:17.845672+00:00",
      "status_notes": "Vulnerability CVE-2018-1257 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1257 affects Spring Framework versions 5.0.x prior to 5.0.6 and 4.3.x prior to 4.3.17 (April 2018). The target version 5.2.11.RELEASE (released November 2020) already contains the upstream fix. The vulnerability allowed DoS attacks via malicious SpEL expressions in STOMP subscription selector headers. The fix has two parts: (1) switching from StandardEvaluationContext to SimpleEvaluati...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1257"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1257 affects Spring Framework versions 5.0.x prior to 5.0.6 and 4.3.x prior to 4.3.17 (April 2018). The target version 5.2.11.RELEASE (released November 2020) already contains the upstream fix. The vulnerability allowed DoS attacks via malicious SpEL expressions in STOMP subscription selector headers. The fix has two parts: (1) switching from StandardEvaluationContext to SimpleEvaluati..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2018-1258 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. CVE-2018-1258 is NOT present in Spring Framework 5.2.11.RELEASE. The vulnerability affected Spring Framework 5.0.5, where method security annotations on JDK dynamic proxies were bypassed due to incorrect target method resolution. The fix (commits aa11721ff0 and f2e77c292d, dated April 2018) was included in upstream Spring Framework 5.1.0.RC1 and all subsequent releases including 5.2.0.RELEASE. The target version 5.2.11.RELEASE (November 2020) inherited the fix from the upstream release when TuxCare onboarded it. The vulnerable code patterns (AopUtils.getMostSpecificMethod excluding proxy classes, missing targetMethod resolution in CacheAspectSupport and ApplicationListenerMethodAdapter) are not present in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.5.RELEASE, < 5.0.6.RELEASE), NVD (= 5.0.5), cve.org (= 5.0.5), Snyk (>= 5.0.5.RELEASE, < 5.0.6.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1258"
      },
      "impact_statement": "CVE-2018-1258 is NOT present in Spring Framework 5.2.11.RELEASE. The vulnerability affected Spring Framework 5.0.5, where method security annotations on JDK dynamic proxies were bypassed due to incorrect target method resolution. The fix (commits aa11721ff0 and f2e77c292d, dated April 2018) was included in upstream Spring Framework 5.1.0.RC1 and all subsequent releases including 5.2.0.RELEASE. The target version 5.2.11.RELEASE (November 2020) inherited the fix from the upstream release when TuxCare onboarded it. The vulnerable code patterns (AopUtils.getMostSpecificMethod excluding proxy classes, missing targetMethod resolution in CacheAspectSupport and ApplicationListenerMethodAdapter) are not present in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.5.RELEASE, < 5.0.6.RELEASE), NVD (= 5.0.5), cve.org (= 5.0.5), Snyk (>= 5.0.5.RELEASE, < 5.0.6.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T18:22:00.126197+00:00",
      "status_notes": "Vulnerability CVE-2018-1271 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1271 directory traversal vulnerability is NOT present in Spring Framework 5.2.11.RELEASE. The upstream fix for URL-encoded path traversal attacks (checking for %2E%2E decoding to ../ or ..\\\\ sequences) was already included in the upstream release before TuxCare onboarding. All defensive code is present in both servlet (spring-webmvc) and reactive (spring-webflux) modules.",
      "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.2.11.RELEASE. The upstream fix for URL-encoded path traversal attacks (checking for %2E%2E decoding to ../ or ..\\\\ sequences) was already included in the upstream release before TuxCare onboarding. All defensive code is present in both servlet (spring-webmvc) and reactive (spring-webflux) modules."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T12:17:09.103452+00:00",
      "status_notes": "Vulnerability CVE-2018-1272 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. CVE-2018-1272 is NOT present in Spring Framework 5.2.11.RELEASE (target SHA e6dfbce6f1). The vulnerability involved predictable multipart boundary generation using java.util.Random, allowing attackers to predict boundaries and inject additional multipart parts. The fix (commit ab2410c754 by Rossen Stoyanchev, March 23, 2018) replaced Random with SecureRandom in MimeTypeUtils.java, making boundaries cryptographically unpredictable. This fix was already present in the upstream Spring Framework 5.2.11.RELEASE when TuxCare onboarded it (commit b1401beb90), confirmed by ancestry analysis showing ab2410c754 is an ancestor of the first TuxCare commit. The target code at spring-core/src/main/java/org/springframework/util/MimeTypeUtils.java:382 contains \"randomToUse = new SecureRandom();\" preventing boundary prediction attacks. Verdict: not_affected (upstream fix, not a TuxCare backport).\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 is NOT present in Spring Framework 5.2.11.RELEASE (target SHA e6dfbce6f1). The vulnerability involved predictable multipart boundary generation using java.util.Random, allowing attackers to predict boundaries and inject additional multipart parts. The fix (commit ab2410c754 by Rossen Stoyanchev, March 23, 2018) replaced Random with SecureRandom in MimeTypeUtils.java, making boundaries cryptographically unpredictable. This fix was already present in the upstream Spring Framework 5.2.11.RELEASE when TuxCare onboarded it (commit b1401beb90), confirmed by ancestry analysis showing ab2410c754 is an ancestor of the first TuxCare commit. The target code at spring-core/src/main/java/org/springframework/util/MimeTypeUtils.java:382 contains \"randomToUse = new SecureRandom();\" preventing boundary prediction attacks. Verdict: not_affected (upstream fix, not a TuxCare backport).\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.15; >= 5.0.0, < 5.0.5), NVD (>= 4.3.0, < 4.3.15; >= 5.0, < 5.0.5), cve.org (< 5.0.5; < 4.3.15), Snyk (>= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; >= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; <= 0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T13:30:30.768655+00:00",
      "status_notes": "Vulnerability CVE-2018-15756 does not affect version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core. The target Spring Framework 5.2.11.RELEASE is NOT affected by CVE-2018-15756. The vulnerability (DoS via malicious Range headers with excessive range count or overlapping ranges) was fixed by upstream Spring maintainer Rossen Stoyanchev (rstoyanchev@pivotal.io) in commit 423aa28ed5, which shipped in the v5.2.11.RELEASE tag before TuxCare onboarded this version. The fix adds: (1) MAX_RANGES=100 limit on range count, and (2) validation that total requested bytes in multi-range requests do not exceed resource length. Both defenses are present and active in the target code at spring-web/src/main/java/org/springframework/http/HttpRange.java and are reached during Range header processing in ResourceHttpRequestHandler.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.1.0.RELEASE, < 5.1.1.RELEASE; >= 5.0.0.RELEASE, < 5.0.10.RELEASE; >= 4.2.0.RELEASE, < 4.3.20.RELEASE), NVD (>= 4.2.0, < 4.3.20; >= 5.0.0, < 5.0.10; = 5.1.0), cve.org (= 5.1; >= 5.0.0, <= 5.0.9; >= 4.3, <= 4.3.19), Snyk (>= 4.2.0.RELEASE, < 4.3.20.RELEASE; >= 5.0.0.RELEASE, < 5.0.10.RELEASE; >= 5.1.0.RELEASE, < 5.1.1.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-15756"
      },
      "impact_statement": "The target Spring Framework 5.2.11.RELEASE is NOT affected by CVE-2018-15756. The vulnerability (DoS via malicious Range headers with excessive range count or overlapping ranges) was fixed by upstream Spring maintainer Rossen Stoyanchev (rstoyanchev@pivotal.io) in commit 423aa28ed5, which shipped in the v5.2.11.RELEASE tag before TuxCare onboarded this version. The fix adds: (1) MAX_RANGES=100 limit on range count, and (2) validation that total requested bytes in multi-range requests do not exceed resource length. Both defenses are present and active in the target code at spring-web/src/main/java/org/springframework/http/HttpRange.java and are reached during Range header processing in ResourceHttpRequestHandler.\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.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2021-22060 affects version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2021-22060"
      },
      "action_statement": "Vulnerability CVE-2021-22060 affects version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2021-22096 affects version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2021-22096"
      },
      "action_statement": "Vulnerability CVE-2021-22096 affects version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-29T03:48:46.502543+00:00",
      "status_notes": "Vulnerability CVE-2024-22233 affects version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2024-22233"
      },
      "action_statement": "Vulnerability CVE-2024-22233 affects version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-05T14:32:00.050379+00:00",
      "status_notes": "Vulnerability CVE-2025-41249 affects version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core, and is fixed in 5.2.11.RELEASE-tuxcare.4.",
      "vulnerability": {
        "name": "CVE-2025-41249"
      },
      "action_statement": "Vulnerability CVE-2025-41249 affects version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core, and is fixed in 5.2.11.RELEASE-tuxcare.4."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.2.11.RELEASE-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-05T14:32:00.050379+00:00",
      "status_notes": "Vulnerability CVE-2026-41848 affects version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core, and is fixed in 5.2.11.RELEASE-tuxcare.4.",
      "vulnerability": {
        "name": "CVE-2026-41848"
      },
      "action_statement": "Vulnerability CVE-2026-41848 affects version 5.2.11.RELEASE-tuxcare.2 of org.springframework:spring-core, and is fixed in 5.2.11.RELEASE-tuxcare.4."
    }
  ]
}