{
  "@id": "urn:uuid:c5edfd43-39f4-463e-ad0b-b18f2ac83747",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 52,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-06T17:29:00.077200+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T12:01:12.972757+00:00",
      "status_notes": "Vulnerability CVE-2009-1190 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. not_affected \u2014 CVE-2009-1190 is fundamentally a JDK vulnerability in the regex engine (Pattern.compile) before JDK 1.6, not a Spring Framework vulnerability. The target Spring Framework 5.3.27-tuxcare.10 runs on Java 8 (8.0.362-librca per .sdkmanrc), which is well beyond JDK 1.6 where the algorithmic complexity issue was fixed. The CVE explicitly requires \"Sun Java Development Kit (JDK) before 1.6\" to exploit...",
      "vulnerability": {
        "name": "CVE-2009-1190"
      },
      "impact_statement": "not_affected \u2014 CVE-2009-1190 is fundamentally a JDK vulnerability in the regex engine (Pattern.compile) before JDK 1.6, not a Spring Framework vulnerability. The target Spring Framework 5.3.27-tuxcare.10 runs on Java 8 (8.0.362-librca per .sdkmanrc), which is well beyond JDK 1.6 where the algorithmic complexity issue was fixed. The CVE explicitly requires \"Sun Java Development Kit (JDK) before 1.6\" to exploit..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-06T17:29:00.077200+00:00",
      "status_notes": "Vulnerability CVE-2011-2730 does not affect version 5.3.27.tuxcare.1 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.3.27 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.3.27 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.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T09:36:00.058799+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. not_affected \u2014 Spring Framework 5.3.27 is not affected by CVE-2011-2894. The vulnerability involves unsafe deserialization of proxy classes allowing remote code execution. The complete fix (acceptProxyClasses flag with NotSerializableException defense in ConfigurableObjectInputStream.resolveProxyClass) was already present in the upstream Spring Framework 5.3.27 release when TuxCare onboarded it. The fix was a...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 5.3.27 is not affected by CVE-2011-2894. The vulnerability involves unsafe deserialization of proxy classes allowing remote code execution. The complete fix (acceptProxyClasses flag with NotSerializableException defense in ConfigurableObjectInputStream.resolveProxyClass) was already present in the upstream Spring Framework 5.3.27 release when TuxCare onboarded it. The fix was a..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-02T17:10:00.096270+00:00",
      "status_notes": "Vulnerability CVE-2014-3578 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. not_affected \u2014 CVE-2014-3578 directory traversal vulnerability is NOT present in Spring Framework 5.3.27. The fix was already included in the upstream Spring Framework 4.1.0 release (May 2014), years before version 5.3.27. The vulnerable code pattern (improper colon handling in path normalization) has been replaced by secure code that rejects treating colons within path segments as URL scheme prefixes.",
      "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.3.27. The fix was already included in the upstream Spring Framework 4.1.0 release (May 2014), years before version 5.3.27. The vulnerable code pattern (improper colon handling in path normalization) has been replaced by secure code that rejects treating colons within path segments as URL scheme prefixes."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T19:05:46.375124+00:00",
      "status_notes": "Vulnerability CVE-2015-0201 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. not_affected \u2014 Spring Framework 5.3.27 is not affected by CVE-2015-0201. The vulnerability concerned predictable session ID generation in the Java SockJS client due to the use of AlternativeJdkIdGenerator, which seeded java.util.Random (a predictable PRNG) once and reused it. The fix was applied in Spring Framework 4.1.5 (January 2015) by replacing AlternativeJdkIdGenerator with JdkIdGenerator, which uses UUI...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-0201"
      },
      "impact_statement": "not_affected \u2014 Spring Framework 5.3.27 is not affected by CVE-2015-0201. The vulnerability concerned predictable session ID generation in the Java SockJS client due to the use of AlternativeJdkIdGenerator, which seeded java.util.Random (a predictable PRNG) once and reused it. The fix was applied in Spring Framework 4.1.5 (January 2015) by replacing AlternativeJdkIdGenerator with JdkIdGenerator, which uses UUI..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T12:54:30.943101+00:00",
      "status_notes": "Vulnerability CVE-2015-5211 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. CVE-2015-5211 (Reflected File Download attack) is NOT present in Spring Framework 5.3.27. The vulnerability was fixed in the upstream Spring Framework in October 2015 (commit 2bd1daa75e by Rossen Stoyanchev), and Spring 5.3.27 (released in 2023) includes this fix as part of the upstream release. The target contains complete defensive code: (1) AbstractMessageConverterMethodProcessor adds Content-Disposition header for unsafe file extensions, (2) AbstractSockJsService validates paths to reject extensions in path parameters, and (3) SAFE_EXTENSIONS whitelist prevents dangerous extensions. This is an upstream vendor fix, not a TuxCare backport.\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 5.3.27. The vulnerability was fixed in the upstream Spring Framework in October 2015 (commit 2bd1daa75e by Rossen Stoyanchev), and Spring 5.3.27 (released in 2023) includes this fix as part of the upstream release. The target contains complete defensive code: (1) AbstractMessageConverterMethodProcessor adds Content-Disposition header for unsafe file extensions, (2) AbstractSockJsService validates paths to reject extensions in path parameters, and (3) SAFE_EXTENSIONS whitelist prevents dangerous extensions. This is an upstream vendor fix, not a TuxCare backport.\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.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T13:07:28.836714+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. CVE-2016-5007 is NOT present in Spring Framework 5.3.27. The vulnerability concerns pattern-matching inconsistencies between Spring Security and Spring MVC that could lead to authorization bypass. The upstream fix (introducing MatchableHandlerMapping API for standardized pattern matching) was released in Spring Framework 4.3.1.RELEASE (April 2016) and is present in version 5.3.27. The fix was authored by upstream Spring Framework developers, not TuxCare, and was already in the release when TuxCare started maintaining this version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.1), NVD (= 3.2.0; = 4.0.0; = 4.1.0; = 4.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 3.2.15; = 3.2.16; = 3.2.17; = 3.2.18; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.1.8; = 4.1.9; = 4.2.1; = 4.2.2; = 4.2.3; = 4.2.4; = 4.2.5; = 4.2.6; = 4.2.7; = 4.2.8; = 4.2.9), cve.org (>= 3.2, < 3.3; >= 4.0, < 4.1; >= 4.1, < 4.2; >= 4.2, < 4.3; < 3.2), Snyk (>= 3.2.0.RELEASE, < 4.3.1.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-5007"
      },
      "impact_statement": "CVE-2016-5007 is NOT present in Spring Framework 5.3.27. The vulnerability concerns pattern-matching inconsistencies between Spring Security and Spring MVC that could lead to authorization bypass. The upstream fix (introducing MatchableHandlerMapping API for standardized pattern matching) was released in Spring Framework 4.3.1.RELEASE (April 2016) and is present in version 5.3.27. The fix was authored by upstream Spring Framework developers, not TuxCare, and was already in the release when TuxCare started maintaining this version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.3.1), NVD (= 3.2.0; = 4.0.0; = 4.1.0; = 4.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 3.2.15; = 3.2.16; = 3.2.17; = 3.2.18; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.1.8; = 4.1.9; = 4.2.1; = 4.2.2; = 4.2.3; = 4.2.4; = 4.2.5; = 4.2.6; = 4.2.7; = 4.2.8; = 4.2.9), cve.org (>= 3.2, < 3.3; >= 4.0, < 4.1; >= 4.1, < 4.2; >= 4.2, < 4.3; < 3.2), Snyk (>= 3.2.0.RELEASE, < 4.3.1.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T13:49:39.156684+00:00",
      "status_notes": "Vulnerability CVE-2018-11040 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. Target version 5.3.27 is not affected by CVE-2018-11040. JSONP support, including the vulnerable automatic parameter handling via \"jsonp\" and \"callback\" query parameters, was completely removed from Spring Framework in upstream commit ac37b678a3 (June 2018) before the 5.3 release line. The target contains neither the MappingJackson2JsonView.jsonpParameterNames field nor the AbstractJsonpResponseBodyAdvice class. This removal was an upstream fix that shipped in the Spring Framework 5.3 release before TuxCare onboarded version 5.3.27.\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": "Target version 5.3.27 is not affected by CVE-2018-11040. JSONP support, including the vulnerable automatic parameter handling via \"jsonp\" and \"callback\" query parameters, was completely removed from Spring Framework in upstream commit ac37b678a3 (June 2018) before the 5.3 release line. The target contains neither the MappingJackson2JsonView.jsonpParameterNames field nor the AbstractJsonpResponseBodyAdvice class. This removal was an upstream fix that shipped in the Spring Framework 5.3 release before TuxCare onboarded version 5.3.27.\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.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T00:55:22.016110+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. not_affected \u2014 Target Spring Framework 5.3.27-tuxcare.10 is NOT affected by CVE-2018-1199. The vulnerability (URL-encoded path traversal bypassing security constraints) was fixed by upstream Spring developers in March 2018 via commit 91b803a2 (SPR-16616). The fix was included in upstream release v5.3.27 (April 2023) before TuxCare onboarded this version. The target contains complete path normalization and val...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 Target Spring Framework 5.3.27-tuxcare.10 is NOT affected by CVE-2018-1199. The vulnerability (URL-encoded path traversal bypassing security constraints) was fixed by upstream Spring developers in March 2018 via commit 91b803a2 (SPR-16616). The fix was included in upstream release v5.3.27 (April 2023) before TuxCare onboarded this version. The target contains complete path normalization and val..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T08:55:17.845672+00:00",
      "status_notes": "Vulnerability CVE-2018-1257 does not affect version 5.3.27.tuxcare.1 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, allowing ReDoS attacks via malicious STOMP selector headers. The target (Spring Framework 5.3.27) is not affected because the fix was already included in the upstream release. The vulnerability pattern is not present in the target code.",
      "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, allowing ReDoS attacks via malicious STOMP selector headers. The target (Spring Framework 5.3.27) is not affected because the fix was already included in the upstream release. The vulnerability pattern is not present in the target code."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:17:29.431970+00:00",
      "status_notes": "Vulnerability CVE-2018-1258 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. CVE-2018-1258 is NOT present in Spring Framework 5.3.27-tuxcare.10. The vulnerability (authorization bypass via incorrect method resolution on proxy classes) was fixed in upstream commits aa11721ff0 and eaff2c28a7 on 2018-04-27, which are ancestors of HEAD and shipped in the upstream 5.3.27 release before TuxCare onboarding. All four patched files (AopUtils.java, AnnotationMethodMatcher.java, CacheAspectSupport.java, ApplicationListenerMethodAdapter.java) contain the complete fix logic. The vulnerable code pattern is not present.\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.3.27-tuxcare.10. The vulnerability (authorization bypass via incorrect method resolution on proxy classes) was fixed in upstream commits aa11721ff0 and eaff2c28a7 on 2018-04-27, which are ancestors of HEAD and shipped in the upstream 5.3.27 release before TuxCare onboarding. All four patched files (AopUtils.java, AnnotationMethodMatcher.java, CacheAspectSupport.java, ApplicationListenerMethodAdapter.java) contain the complete fix logic. The vulnerable code pattern is not present.\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.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T18:22:00.126197+00:00",
      "status_notes": "Vulnerability CVE-2018-1271 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. not_affected \u2014 CVE-2018-1271 directory traversal vulnerability is NOT present in Spring Framework 5.3.27. The upstream fix from March 2018 (SPR-16616) shipped in the 5.3.27 release. The defense code URL-decodes resource paths and rejects those containing encoded directory traversal sequences (../ or ..\\). Target version 5.3.27 is much newer than affected versions (5.0 < 5.0.5, 4.3 < 4.3.15). Fix authored by P...",
      "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.3.27. The upstream fix from March 2018 (SPR-16616) shipped in the 5.3.27 release. The defense code URL-decodes resource paths and rejects those containing encoded directory traversal sequences (../ or ..\\). Target version 5.3.27 is much newer than affected versions (5.0 < 5.0.5, 4.3 < 4.3.15). Fix authored by P..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T12:18:14.184922+00:00",
      "status_notes": "Vulnerability CVE-2018-1272 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. CVE-2018-1272 affects Spring Framework 5.0 < 5.0.5 and 4.3 < 4.3.15, enabling multipart boundary injection attacks when applications forward requests to downstream servers. The vulnerability stems from using predictable Random for boundary generation, allowing attackers to craft input with pre-computed boundaries that override legitimate field values (e.g., username, roles). The fix replaces Random with SecureRandom in MimeTypeUtils.java. Target version 5.3.27 is not affected\u2014the fix was already present in the upstream Spring Framework 5.3.27 release (commit ab2410c754 by rstoyanchev@pivotal.io), predating TuxCare's onboarding. The vulnerable code pattern never existed in this version.\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 affects Spring Framework 5.0 < 5.0.5 and 4.3 < 4.3.15, enabling multipart boundary injection attacks when applications forward requests to downstream servers. The vulnerability stems from using predictable Random for boundary generation, allowing attackers to craft input with pre-computed boundaries that override legitimate field values (e.g., username, roles). The fix replaces Random with SecureRandom in MimeTypeUtils.java. Target version 5.3.27 is not affected\u2014the fix was already present in the upstream Spring Framework 5.3.27 release (commit ab2410c754 by rstoyanchev@pivotal.io), predating TuxCare's onboarding. The vulnerable code pattern never existed in this version.\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.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T13:31:13.211032+00:00",
      "status_notes": "Vulnerability CVE-2018-15756 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. CVE-2018-15756 does not affect Spring Framework 5.3.27. The vulnerability involved denial of service through malicious HTTP Range headers with excessive ranges or overlapping ranges. The fix (limiting ranges to 100 and validating sum < resource length) was already present in the upstream Spring Framework 5.3.27 release, authored by Rossen Stoyanchev (rstoyanchev@pivotal.io) in commit 423aa28ed. TuxCare onboarded this already-fixed upstream version. The vulnerable code pattern is not present 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": "CVE-2018-15756 does not affect Spring Framework 5.3.27. The vulnerability involved denial of service through malicious HTTP Range headers with excessive ranges or overlapping ranges. The fix (limiting ranges to 100 and validating sum < resource length) was already present in the upstream Spring Framework 5.3.27 release, authored by Rossen Stoyanchev (rstoyanchev@pivotal.io) in commit 423aa28ed. TuxCare onboarded this already-fixed upstream version. The vulnerable code pattern is not present 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": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-31T20:10:47.926892+00:00",
      "status_notes": "Vulnerability CVE-2021-22060 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. not_affected \u2014 Target repository Spring Framework 5.3.27 is NOT vulnerable to CVE-2021-22060. The vulnerability (log injection via newline and control characters) was fixed in the upstream Spring Framework release with commits 99c7608f (Dec 8, 2021) adding newline/control-character sanitization to LogFormatUtils, and e9083d7d (Dec 9, 2021) applying LogFormatUtils across web resource handlers and websocket cod...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22060"
      },
      "impact_statement": "not_affected \u2014 Target repository Spring Framework 5.3.27 is NOT vulnerable to CVE-2021-22060. The vulnerability (log injection via newline and control characters) was fixed in the upstream Spring Framework release with commits 99c7608f (Dec 8, 2021) adding newline/control-character sanitization to LogFormatUtils, and e9083d7d (Dec 9, 2021) applying LogFormatUtils across web resource handlers and websocket cod..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-31T21:12:52.953367+00:00",
      "status_notes": "Vulnerability CVE-2021-22096 does not affect version 5.3.27.tuxcare.1 of org.springframework:spring-core. not_affected \u2014 The target (Spring Framework 5.3.27-tuxcare.10) is NOT affected by CVE-2021-22096 (log injection vulnerability). The vulnerability allowed attackers to inject newline and control characters into log entries, creating forged log entries. The upstream fix was already present in the base release v5.3.14 that TuxCare onboarded, before any TuxCare modifications. Both key fix commits (99c7608ffe addi...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22096"
      },
      "impact_statement": "not_affected \u2014 The target (Spring Framework 5.3.27-tuxcare.10) is NOT affected by CVE-2021-22096 (log injection vulnerability). The vulnerability allowed attackers to inject newline and control characters into log entries, creating forged log entries. The upstream fix was already present in the base release v5.3.14 that TuxCare onboarded, before any TuxCare modifications. Both key fix commits (99c7608ffe addi..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-29T03:48:46.502543+00:00",
      "status_notes": "Vulnerability CVE-2024-22233 affects version 5.3.27.tuxcare.1 of org.springframework:spring-core.",
      "vulnerability": {
        "name": "CVE-2024-22233"
      },
      "action_statement": "Vulnerability CVE-2024-22233 affects version 5.3.27.tuxcare.1 of org.springframework:spring-core."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-41249 affects version 5.3.27.tuxcare.1 of org.springframework:spring-core, and is fixed in 5.3.27-tuxcare.4.",
      "vulnerability": {
        "name": "CVE-2025-41249"
      },
      "action_statement": "Vulnerability CVE-2025-41249 affects version 5.3.27.tuxcare.1 of org.springframework:spring-core, and is fixed in 5.3.27-tuxcare.4."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework/spring-core@5.3.27.tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-41848 affects version 5.3.27.tuxcare.1 of org.springframework:spring-core, and is fixed in 5.3.27-tuxcare.10.",
      "vulnerability": {
        "name": "CVE-2026-41848"
      },
      "action_statement": "Vulnerability CVE-2026-41848 affects version 5.3.27.tuxcare.1 of org.springframework:spring-core, and is fixed in 5.3.27-tuxcare.10."
    }
  ]
}