{
  "@id": "urn:uuid:dcc7a71f-2c78-474b-a4a6-7d67e6526031",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 50,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-06T17:30:26.757723+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-10-30T12:03:27.225837+00:00",
      "status_notes": "Vulnerability CVE-2009-1190 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.0.23 is not affected by CVE-2009-1190. While the code pattern (serializable JdkRegexpMethodPointcut calling Pattern.compile without validation) exists in the codebase, the underlying JDK vulnerability (algorithmic complexity in Pattern.compile) was fixed by Oracle/Sun in JDK 1.6. Spring Framework 6.0.23 requires JDK 17 as its minimum runtime, making it impossible to deploy on...",
      "vulnerability": {
        "name": "CVE-2009-1190"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.0.23 is not affected by CVE-2009-1190. While the code pattern (serializable JdkRegexpMethodPointcut calling Pattern.compile without validation) exists in the codebase, the underlying JDK vulnerability (algorithmic complexity in Pattern.compile) was fixed by Oracle/Sun in JDK 1.6. Spring Framework 6.0.23 requires JDK 17 as its minimum runtime, making it impossible to deploy on..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-11-06T17:30:26.757723+00:00",
      "status_notes": "Vulnerability CVE-2011-2730 does not affect version 6.0.23-tuxcare.12 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 6.0.23 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 6.0.23 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@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-11-03T09:38:00.146680+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.0.23 is not affected by CVE-2011-2894. The vulnerability was in RMI remoting support (Spring 3.0.0-3.0.5) where RemoteInvocationSerializingExporter deserializedproxy classes without validation. The upstream vendor (Juergen Hoeller) added the acceptProxyClasses defense in July 2011 (commit 7d8aa05c40), which was shipped in the upstream release before TuxCare onboarding. Additi...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.0.23 is not affected by CVE-2011-2894. The vulnerability was in RMI remoting support (Spring 3.0.0-3.0.5) where RemoteInvocationSerializingExporter deserializedproxy classes without validation. The upstream vendor (Juergen Hoeller) added the acceptProxyClasses defense in July 2011 (commit 7d8aa05c40), which was shipped in the upstream release before TuxCare onboarding. Additi..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-11-02T17:10:00.096270+00:00",
      "status_notes": "Vulnerability CVE-2014-3578 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. not_affected \u2014 CVE-2014-3578 is NOT present in Spring Framework 6.0.23-tuxcare.12. The vulnerability was a directory traversal flaw in StringUtils.cleanPath() that allowed attackers to read arbitrary files via crafted URLs with embedded colons (e.g., /a/:b/../../sensitive.txt). The upstream fix (commit 8ee4651038) was already included in the Spring Framework release that TuxCare onboarded, predating TuxCare's...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-3578"
      },
      "impact_statement": "not_affected \u2014 CVE-2014-3578 is NOT present in Spring Framework 6.0.23-tuxcare.12. The vulnerability was a directory traversal flaw in StringUtils.cleanPath() that allowed attackers to read arbitrary files via crafted URLs with embedded colons (e.g., /a/:b/../../sensitive.txt). The upstream fix (commit 8ee4651038) was already included in the Spring Framework release that TuxCare onboarded, predating TuxCare's..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-11-03T19:06:53.108630+00:00",
      "status_notes": "Vulnerability CVE-2015-0201 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5, where the Java SockJS client generated predictable session IDs using AlternativeJdkIdGenerator (which used java.util.Random after initial SecureRandom seeding). The vulnerability was fixed in Spring Framework 4.1.5 (January 2015) by switching to JdkIdGenerator, which uses UUID.randomUUID() with cryptographically secure randomness. The t...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-0201"
      },
      "impact_statement": "not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5, where the Java SockJS client generated predictable session IDs using AlternativeJdkIdGenerator (which used java.util.Random after initial SecureRandom seeding). The vulnerability was fixed in Spring Framework 4.1.5 (January 2015) by switching to JdkIdGenerator, which uses UUID.randomUUID() with cryptographically secure randomness. The t..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-11-03T12:55:53.618169+00:00",
      "status_notes": "Vulnerability CVE-2015-5211 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. CVE-2015-5211 (Reflected File Download attack) is NOT present in Spring Framework 6.0.23-tuxcare.12. The vulnerability was fixed in the upstream release before TuxCare onboarding. The defense code in AbstractMessageConverterMethodProcessor.java (lines 438-518) implements comprehensive RFD protection: extracts file extensions from both URL filename and path parameters, decodes them to prevent encoding bypasses, and adds Content-Disposition header with safe filename (f.txt) if the extension is not in the safe whitelist. The fix was authored by upstream Spring Framework maintainer Rossen Stoyanchev (rstoyanchev@pivotal.io) in commit 2bd1daa, which predates the first TuxCare commit 73315ed2.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.2.0, < 4.2.2; >= 4.0.0, < 4.1.8; < 3.2.15), NVD (= 3.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.0; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.2.0; = 4.2.1), Snyk (>= 3.2.0.RELEASE, < 3.2.15.RELEASE; >= 4.0.0.RELEASE, < 4.1.8.RELEASE; >= 4.2.0.RELEASE, < 4.2.2.RELEASE; <= 0; <= 0).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-5211"
      },
      "impact_statement": "CVE-2015-5211 (Reflected File Download attack) is NOT present in Spring Framework 6.0.23-tuxcare.12. The vulnerability was fixed in the upstream release before TuxCare onboarding. The defense code in AbstractMessageConverterMethodProcessor.java (lines 438-518) implements comprehensive RFD protection: extracts file extensions from both URL filename and path parameters, decodes them to prevent encoding bypasses, and adds Content-Disposition header with safe filename (f.txt) if the extension is not in the safe whitelist. The fix was authored by upstream Spring Framework maintainer Rossen Stoyanchev (rstoyanchev@pivotal.io) in commit 2bd1daa, which predates the first TuxCare commit 73315ed2.\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@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-11-03T13:08:13.759745+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. Spring Framework 6.0.23 is not affected by CVE-2016-5007. The vulnerability involved pattern matching divergence between Spring Security's authorization checks and Spring MVC's controller routing, allowing attackers to bypass security by crafting requests that Spring Security didn't recognize as protected but Spring MVC routed to protected controllers. The upstream fix (commit 16949941f83) introduced the MatchableHandlerMapping API and HandlerMappingIntrospector to expose Spring MVC's exact pattern matching logic to Spring Security, eliminating the divergence. This fix was authored by jhoeller@pivotal.io and shipped in the upstream Spring Framework release, predating TuxCare's first commit (73315ed209). Both AbstractUrlHandlerMapping and RequestMappingHandlerMapping implement MatchableHandlerMapping with properly functioning match() methods. The vulnerable pattern is not present in version 6.0.23.\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": "Spring Framework 6.0.23 is not affected by CVE-2016-5007. The vulnerability involved pattern matching divergence between Spring Security's authorization checks and Spring MVC's controller routing, allowing attackers to bypass security by crafting requests that Spring Security didn't recognize as protected but Spring MVC routed to protected controllers. The upstream fix (commit 16949941f83) introduced the MatchableHandlerMapping API and HandlerMappingIntrospector to expose Spring MVC's exact pattern matching logic to Spring Security, eliminating the divergence. This fix was authored by jhoeller@pivotal.io and shipped in the upstream Spring Framework release, predating TuxCare's first commit (73315ed209). Both AbstractUrlHandlerMapping and RequestMappingHandlerMapping implement MatchableHandlerMapping with properly functioning match() methods. The vulnerable pattern is not present in version 6.0.23.\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@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-11-03T13:50:27.486705+00:00",
      "status_notes": "Vulnerability CVE-2018-11040 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. Spring Framework 6.0.23 is not affected by CVE-2018-11040. JSONP support was completely removed from the upstream Spring Framework codebase in version 5.1.0 (commit ac37b678a3 by Sebastien Deleuze on June 7, 2018). The target version 6.0.23 inherits this removal from the upstream release - the JSONP removal predates TuxCare's onboarding of this version branch. All JSONP-related code has been deleted: MappingJackson2JsonView no longer contains jsonpParameterNames or JSONP processing methods, AbstractJsonpResponseBodyAdvice class was deleted, MappingJacksonValue no longer has setJsonpFunction/getJsonpFunction methods, and SockJS JSONP transport handlers were removed. The vulnerability pattern cannot exist because the entire JSONP feature has been eliminated 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 6.0.23 is not affected by CVE-2018-11040. JSONP support was completely removed from the upstream Spring Framework codebase in version 5.1.0 (commit ac37b678a3 by Sebastien Deleuze on June 7, 2018). The target version 6.0.23 inherits this removal from the upstream release - the JSONP removal predates TuxCare's onboarding of this version branch. All JSONP-related code has been deleted: MappingJackson2JsonView no longer contains jsonpParameterNames or JSONP processing methods, AbstractJsonpResponseBodyAdvice class was deleted, MappingJacksonValue no longer has setJsonpFunction/getJsonpFunction methods, and SockJS JSONP transport handlers were removed. The vulnerability pattern cannot exist because the entire JSONP feature has been eliminated 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@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-11-03T00:54:45.999289+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.0.23 is not affected by CVE-2018-1199. The vulnerability, which allowed bypassing security constraints via URL path parameters with special encodings (duplicate slashes, backslashes, encoded traversal sequences), was fixed by the upstream vendor (Spring/VMware) in commits for SPR-16616, SPR-16296, and SPR-16526. These fixes were included in Spring Framework 5.0.3 (released Ma...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.0.23 is not affected by CVE-2018-1199. The vulnerability, which allowed bypassing security constraints via URL path parameters with special encodings (duplicate slashes, backslashes, encoded traversal sequences), was fixed by the upstream vendor (Spring/VMware) in commits for SPR-16616, SPR-16296, and SPR-16526. These fixes were included in Spring Framework 5.0.3 (released Ma..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-10-30T09:01:17.494754+00:00",
      "status_notes": "Vulnerability CVE-2018-1257 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1257 affects Spring Framework versions with unconditional STOMP selector header parsing vulnerable to ReDoS. The target (6.0.23) contains the upstream fix from commit ff2228fdaf by rstoyanchev@pivotal.io that adds the ability to disable selector parsing via setSelectorHeaderName(null) and guards parsing with a null check. This fix was already present in the upstream Spring Framework 6....",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1257"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1257 affects Spring Framework versions with unconditional STOMP selector header parsing vulnerable to ReDoS. The target (6.0.23) contains the upstream fix from commit ff2228fdaf by rstoyanchev@pivotal.io that adds the ability to disable selector parsing via setSelectorHeaderName(null) and guards parsing with a null check. This fix was already present in the upstream Spring Framework 6...."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2018-1258 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. CVE-2018-1258 authorization bypass vulnerability is NOT present in Spring Framework 6.0.23. The upstream fixes (commits aa11721ff0 and eaff2c28a7) were already included in the upstream Spring Framework release that TuxCare onboarded. The vulnerability involved incorrect method resolution for JDK dynamic proxies, causing security annotations to be missed during authorization checks. Both required fixes are present in the target code: (1) AopUtils.getMostSpecificMethod no longer skips proxy classes, (2) AnnotationMethodMatcher returns false early for proxy classes, and (3) CacheAspectSupport and ApplicationListenerMethodAdapter explicitly check for proxy classes before method resolution. Author: jhoeller@pivotal.io (upstream Spring team).\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.0.5.RELEASE, < 5.0.6.RELEASE), NVD (= 5.0.5), cve.org (= 5.0.5), Snyk (>= 5.0.5.RELEASE, < 5.0.6.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1258"
      },
      "impact_statement": "CVE-2018-1258 authorization bypass vulnerability is NOT present in Spring Framework 6.0.23. The upstream fixes (commits aa11721ff0 and eaff2c28a7) were already included in the upstream Spring Framework release that TuxCare onboarded. The vulnerability involved incorrect method resolution for JDK dynamic proxies, causing security annotations to be missed during authorization checks. Both required fixes are present in the target code: (1) AopUtils.getMostSpecificMethod no longer skips proxy classes, (2) AnnotationMethodMatcher returns false early for proxy classes, and (3) CacheAspectSupport and ApplicationListenerMethodAdapter explicitly check for proxy classes before method resolution. Author: jhoeller@pivotal.io (upstream Spring team).\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@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-10-30T18:28:50.149316+00:00",
      "status_notes": "Vulnerability CVE-2018-1271 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1271 (Windows directory traversal via backslash path sequences) is NOT present in Spring Framework 6.0.23-tuxcare.12. The vulnerability allowed attackers to use URL-encoded backslashes (%5C) in resource paths to bypass traversal checks on Windows systems. The upstream fix (commit f59ea610dfcf55cd0b42f6dd76a9b3dab0218aaa by jhoeller@pivotal.io, March 2018) added validation for both forw...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1271"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1271 (Windows directory traversal via backslash path sequences) is NOT present in Spring Framework 6.0.23-tuxcare.12. The vulnerability allowed attackers to use URL-encoded backslashes (%5C) in resource paths to bypass traversal checks on Windows systems. The upstream fix (commit f59ea610dfcf55cd0b42f6dd76a9b3dab0218aaa by jhoeller@pivotal.io, March 2018) added validation for both forw..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-11-03T12:18:14.184922+00:00",
      "status_notes": "Vulnerability CVE-2018-1272 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. CVE-2018-1272 is not present in Spring Framework 6.0.23. The vulnerability involved predictable multipart boundary generation using java.util.Random, allowing attackers to inject forged multipart parts. The fix (switching to SecureRandom) was applied by upstream Spring developer Rossen Stoyanchev on 2018-03-23 in commit ab2410c754 as part of v5.0.5.RELEASE. Since the target version 6.0.23 is much newer than 5.0.5.RELEASE, the fix was already present in the upstream release that TuxCare onboarded. The vulnerable code pattern is not present in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.15; >= 5.0.0, < 5.0.5), NVD (>= 4.3.0, < 4.3.15; >= 5.0, < 5.0.5), cve.org (< 5.0.5; < 4.3.15), Snyk (>= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; >= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; <= 0).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1272"
      },
      "impact_statement": "CVE-2018-1272 is not present in Spring Framework 6.0.23. The vulnerability involved predictable multipart boundary generation using java.util.Random, allowing attackers to inject forged multipart parts. The fix (switching to SecureRandom) was applied by upstream Spring developer Rossen Stoyanchev on 2018-03-23 in commit ab2410c754 as part of v5.0.5.RELEASE. Since the target version 6.0.23 is much newer than 5.0.5.RELEASE, the fix was already present in the upstream release that TuxCare onboarded. The vulnerable code pattern is not present in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.15; >= 5.0.0, < 5.0.5), NVD (>= 4.3.0, < 4.3.15; >= 5.0, < 5.0.5), cve.org (< 5.0.5; < 4.3.15), Snyk (>= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; >= 4.3.0.RELEASE, < 4.3.14.RELEASE; >= 5.0.0.RELEASE, < 5.0.5.RELEASE; <= 0)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-11-03T13:32:59.098532+00:00",
      "status_notes": "Vulnerability CVE-2018-15756 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. CVE-2018-15756 is not present in Spring Framework 6.0.23-tuxcare.12. The vulnerability concerned unbounded HTTP Range header processing leading to denial of service. The upstream fix (commit 423aa28ed5 by Rossen Stoyanchev) was already included in the Spring Framework 6.0.x release that TuxCare onboarded. The fix adds MAX_RANGES=100 limit and validates that sum of all range byte-counts is less than resource length, preventing both excessive range count and overlapping range attacks. These protections are present in HEAD at spring-web/src/main/java/org/springframework/http/HttpRange.java lines 48, 136-138, and 185-195.\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 is not present in Spring Framework 6.0.23-tuxcare.12. The vulnerability concerned unbounded HTTP Range header processing leading to denial of service. The upstream fix (commit 423aa28ed5 by Rossen Stoyanchev) was already included in the Spring Framework 6.0.x release that TuxCare onboarded. The fix adds MAX_RANGES=100 limit and validates that sum of all range byte-counts is less than resource length, preventing both excessive range count and overlapping range attacks. These protections are present in HEAD at spring-web/src/main/java/org/springframework/http/HttpRange.java lines 48, 136-138, and 185-195.\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": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-10-31T20:14:30.754022+00:00",
      "status_notes": "Vulnerability CVE-2021-22060 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. not_affected \u2014 The target Spring Framework 6.0.23 is not affected by CVE-2021-22060 (log injection vulnerability). The vulnerability affected versions 5.3.0-5.3.13, 5.2.0-5.2.18, and older. The fix was introduced by upstream Spring Framework in v5.3.14 (December 2021) and is present in the target version, which is a newer major release. The fix sanitizes user-controllable data in log messages by replacing new...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22060"
      },
      "impact_statement": "not_affected \u2014 The target Spring Framework 6.0.23 is not affected by CVE-2021-22060 (log injection vulnerability). The vulnerability affected versions 5.3.0-5.3.13, 5.2.0-5.2.18, and older. The fix was introduced by upstream Spring Framework in v5.3.14 (December 2021) and is present in the target version, which is a newer major release. The fix sanitizes user-controllable data in log messages by replacing new..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-10-31T21:16:51.996676+00:00",
      "status_notes": "Vulnerability CVE-2021-22096 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. not_affected \u2014 Spring Framework 6.0.23-tuxcare.12 is NOT affected by CVE-2021-22096. The upstream fix for log injection prevention was already present in the Spring Framework 6.0.x release that TuxCare onboarded. The fix (commit 99c7608ffe by Rossen Stoyanchev @vmware.com, Dec 2021) implements comprehensive input sanitization in LogFormatUtils.formatValue() that replaces newline characters with &lt;EOL&gt; an...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22096"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 6.0.23-tuxcare.12 is NOT affected by CVE-2021-22096. The upstream fix for log injection prevention was already present in the Spring Framework 6.0.x release that TuxCare onboarded. The fix (commit 99c7608ffe by Rossen Stoyanchev @vmware.com, Dec 2021) implements comprehensive input sanitization in LogFormatUtils.formatValue() that replaces newline characters with &lt;EOL&gt; an..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-11-04T09:18:58.233822+00:00",
      "status_notes": "Vulnerability CVE-2024-22233 does not affect version 6.0.23-tuxcare.12 of org.springframework:spring-core. CVE-2024-22233 describes two DoS vulnerabilities in Spring Framework 6.0.15 and 6.1.2: (1) malformed forwarded headers causing uncaught exceptions in ForwardedHeaderFilter, and (2) URIs containing regex metacharacters causing PatternSyntaxException in HandlerMappingIntrospector. Both vulnerabilities have been fixed by upstream patches that shipped in Spring Framework 6.0.23 before TuxCare onboarded this version. The target at version 6.0.23-tuxcare.12 contains both fixes: ForwardedHeaderFilter wraps header parsing in try-catch returning HTTP 400 on error, and HandlerMappingIntrospector uses .equals() instead of .matches() for URI comparison. No vulnerable code patterns remain.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 6.1.2, < 6.1.3; >= 6.0.15, < 6.0.16), NVD (= 6.0.15; = 6.1.2), cve.org (= 6.1.2; = 6.0.15), Snyk (>= 6.0.15, < 6.0.16; >= 6.1.2, < 6.1.3).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-22233"
      },
      "impact_statement": "CVE-2024-22233 describes two DoS vulnerabilities in Spring Framework 6.0.15 and 6.1.2: (1) malformed forwarded headers causing uncaught exceptions in ForwardedHeaderFilter, and (2) URIs containing regex metacharacters causing PatternSyntaxException in HandlerMappingIntrospector. Both vulnerabilities have been fixed by upstream patches that shipped in Spring Framework 6.0.23 before TuxCare onboarded this version. The target at version 6.0.23-tuxcare.12 contains both fixes: ForwardedHeaderFilter wraps header parsing in try-catch returning HTTP 400 on error, and HandlerMappingIntrospector uses .equals() instead of .matches() for URI comparison. No vulnerable code patterns remain.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 6.1.2, < 6.1.3; >= 6.0.15, < 6.0.16), NVD (= 6.0.15; = 6.1.2), cve.org (= 6.1.2; = 6.0.15), Snyk (>= 6.0.15, < 6.0.16; >= 6.1.2, < 6.1.3)."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-10-21T17:09:08.806510+00:00",
      "status_notes": "Vulnerability CVE-2025-41249 is fixed in version 6.0.23-tuxcare.12 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2025-41249"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@6.0.23-tuxcare.12"
          }
        }
      ],
      "timestamp": "2026-10-21T17:09:08.806510+00:00",
      "status_notes": "Vulnerability CVE-2026-41848 is fixed in version 6.0.23-tuxcare.12 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2026-41848"
      }
    }
  ]
}