{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:6c34f47b-caac-5d71-a788-94182262131f",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "spring-security-core",
      "purl": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1",
      "type": "library",
      "group": "org.springframework.security",
      "bom-ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1",
      "version": "5.0.18.RELEASE-tuxcare.1",
      "pedigree": {
        "ancestors": [
          {
            "name": "spring-security-core",
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE",
            "type": "library",
            "group": "org.springframework.security",
            "version": "5.0.18.RELEASE"
          }
        ]
      },
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2010-3700",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:8b41fb72-3aee-5bed-af5a-82c0a057027b",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2010-3700 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2010-3700 is not present in Spring Security 5.0.18.RELEASE. The upstream fix (SEC-1584, commit 7d97adc687) was already shipped in this release before TuxCare onboarded it. The fix implements HttpFirewall with RequestWrapper that strips path parameters from servletPath and pathInfo before security pattern matching, preventing attackers from bypassing security constraints via malicious path p...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2011-2731",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:890e5bfb-243e-5a1b-9c75-98feb76e599e",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2011-2731 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2011-2731 concerns a race condition in RunAsManager where the Authentication object was stored in a shared SecurityContext, allowing privilege escalation via crafted threads. The upstream Spring Security project fixed this vulnerability in two commits: SEC-1750 (July 2011) and SEC-1967 (July 2012). Both fixes are present in the target version 5.0.18.RELEASE at HEAD (8f2a63e122). The fixes w...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2011-2732",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:c12dc541-7d8c-5010-9373-821ad6b6fddc",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2011-2732 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2011-2732 (CRLF injection in Spring Security logout functionality via spring-security-redirect parameter) is NOT AFFECTED in target version 5.0.18.RELEASE. The vulnerability was fixed by upstream Spring Security developers in June 2016 (commit 26fa4a4bf by Edd\u00fa Mel\u00e9ndez), and this fix was already included in the 5.0.18.RELEASE that TuxCare onboarded. The target contains comprehensive CRLF v...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2011-2894",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:b6e0a7a0-1a33-563e-85a8-54bfdcc9d44d",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2011-2894 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 The target Spring Security 5.0.18.RELEASE is NOT affected by CVE-2011-2894. The vulnerability (unsafe deserialization of SecurityContext objects in RMI remoting) was fixed by upstream Spring Security in commit b48fc53fa2 on May 20, 2011, before the 5.0.18.RELEASE was published. The fix was already present when TuxCare onboarded this version on Sept 16, 2026. The vulnerable code pattern (seriali...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2012-5055",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:431a19fc-8154-5a8d-a161-c02be5d21f28",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2012-5055 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2012-5055 is NOT present in Spring Security 5.0.18.RELEASE. The timing attack vulnerability was fixed by upstream Spring Security in September 2012 (commit c076f0f2e1, SEC-2056) by Rob Winch. This fix shipped with the upstream 5.0.18.RELEASE that TuxCare onboarded, so the vulnerable code pattern never existed in this target version. The target contains complete timing attack mitigation: it ...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2014-0097",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:bcc42fbb-06ea-5eff-adcf-ab2cb7eb9a14",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2014-0097 affects version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2014-3527",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:9f4e64e2-674e-573f-ac21-9d8673ac78b3",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2014-3527 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. CVE-2014-3527 is not present in Spring Security 5.0.18.RELEASE. The vulnerability involved CAS proxy ticket authentication using untrusted HTTP Host headers to construct the service URL, allowing a malicious CAS Service to bypass access control restrictions. The fix (commit 934937d9c1dc20c396b96c08310b72cfa627acbf by Rob Winch) was already included in the upstream release 5.0.18.RELEASE when TuxCare onboarded it. The fixed code uses the configured CAS service URL (from ServiceProperties) instead of HttpServletRequest headers to build the service URL, preventing the attack.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-5007",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:6bc086ff-2bd2-58f0-b3a9-f1b5a8dc0dfb",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-5007 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. CVE-2016-5007 addresses path-matching discrepancies between Spring Security and Spring MVC that could allow authorization bypass. The target repository at version 5.0.18.RELEASE contains both upstream fixes: (1) DefaultHttpFirewall with URL-encoded slash blocking (active by default), and (2) MvcRequestMatcher for Spring MVC-aligned path matching (opt-in API). Both fixes were authored by the upstream Spring Security team (Rob Winch, rwinch@gopivotal.com) in 2016 and shipped in the upstream 5.0.18.RELEASE that TuxCare later onboarded. The critical defense (encoded slash blocking) runs automatically on every request, preventing the primary attack vector described in the CVE. The vulnerable pattern is not present.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.1.1), 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; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.1.0), cve.org (>= 3.2, < 3.3; >= 4.0, < 4.1; = 4.1.0), Snyk (>= 3.2.0.RELEASE, < 4.1.1.RELEASE; >= 3.2.0.RELEASE, < 4.1.1.RELEASE).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2016-9879",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:56f4f00a-6840-595f-b1cf-ac80af3101d3",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2016-9879 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. Spring Security 5.0.18.RELEASE is not affected by CVE-2016-9879. The vulnerability allows bypassing security constraints by adding URL-encoded slashes (%2f/%2F) in path parameters. The fix was already present in the upstream Spring Security 5.0.18.RELEASE when TuxCare onboarded this version. The defense code in DefaultHttpFirewall.java (lines 60-63, 91-101) checks the raw requestURI for %2f/%2F patterns and rejects such requests with RequestRejectedException by default. Fix commit 666e356ebc was authored by Rob Winch (rwinch@gopivotal.com) from upstream and is an ancestor of the first TuxCare commit f4c524d98b.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 3.2.10.RELEASE; >= 4.0.0.RELEASE, < 4.1.4.RELEASE; >= 4.2.0.RELEASE, < 4.2.1.RELEASE), 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; = 4.1.0; = 4.1.1; = 4.1.2; = 4.1.3; = 4.2.0), Snyk (>= 3.2.0.RELEASE, < 3.2.10.RELEASE; >= 4.0.0.RELEASE, < 4.1.4.RELEASE; >= 4.2.0.RELEASE, < 4.2.1.RELEASE; <= 0).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2017-4995",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:676294a7-4e9d-5562-8d63-ed32a7542e15",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2017-4995 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. The target Spring Security 5.0.18.RELEASE is not affected by CVE-2017-4995. The vulnerability concerned Jackson deserialization with unrestricted default typing in Spring Security's SecurityJackson2Modules.enableDefaultTyping() method, allowing arbitrary code execution through deserialization gadgets. The upstream fix (commit 5dee8534cd by Rob Winch, May 31, 2017) replaced unrestricted type resolution with a whitelist-based TypeIdResolver that rejects classes unless they are whitelisted, have explicit mixins, or have Jackson annotations. This fix was committed before Spring Security 5.0.0.RELEASE (November 2017) and was already present in the upstream 5.0.18.RELEASE release when TuxCare onboarded it (first TuxCare commit f4c524d98bf, Onboard version 5.0.18.RELEASE). The CVE lists only 5.0.0.M1 (milestone/pre-release) as affected in the 5.0.x line, not GA releases.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.2.0.RELEASE, < 4.2.3.RELEASE; >= 5.0.0.M1, < 5.0.0.M2), NVD (= 4.2.0-release; = 4.2.1-release; = 4.2.2-release; = 5.0.0-m1), cve.org (= 4.2.0.RELEASE; = 4.2.2.RELEASE; = 5.0.0.M1), Snyk (>= 4.2.0.RELEASE, < 4.2.3.RELEASE).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2018-1199",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:6fc21aa1-e7d3-5d74-965f-7684471195ad",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2018-1199 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2018-1199 is NOT present in Spring Security 5.0.18.RELEASE. The vulnerability allowed bypassing security constraints via URL path parameters containing semicolons with special encodings. The upstream fix (commit 0eef5b4b42 by Rob Winch) introduced StrictHttpFirewall which rejects requests containing semicolons by default. This fix was already included in the upstream 5.0.18.RELEASE that Tux...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2018-15801",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:31292433-59bf-5234-b6bb-8123a0581f2f",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2018-15801 affects version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2019-11272",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:6d4a0a7e-6ece-5ce9-a955-3e6e7a755d8e",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2019-11272 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. Spring Security 5.0.18.RELEASE is not affected by CVE-2019-11272. The vulnerable class PlaintextPasswordEncoder does not exist in this version - it was removed from Spring Security 5.x in October 2017 (upstream commit 12dbf2e961) as part of an architectural migration from the authentication.encoding package to the new crypto package. The CVE explicitly affects versions 4.2.x up to 4.2.12 and older unsupported versions. Spring Security 5.0.18.RELEASE uses NoOpPasswordEncoder and other crypto-based encoders which correctly handle null passwords.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.2.13; < 4.2.13.RELEASE), NVD (< 4.2.13), cve.org (>= 4.2, < 4.2.13.RELEASE), Snyk (>= 4.2.0.RELEASE, < 4.2.13.RELEASE).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2019-3795",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:79bf44f2-d09f-54d6-b940-93ccc5cf9683",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2019-3795 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2019-3795 affects Spring Security versions 5.0.x prior to 5.0.12. The target is version 5.0.18.RELEASE, which already contains the upstream fix. The vulnerability involved insecure randomness when using SecureRandomFactoryBean#setSeed - calling setSeed() on an uninitialized SecureRandom would replace the entire internal state with the user-provided seed, making the output predictable. The f...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2020-5407",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:bccf6a8f-357a-575a-a1c8-c636663ca0c9",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2020-5407 affects version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2020-5408",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:bdd27235-3ea8-5ce0-81b9-3df2db0a4307",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2020-5408 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 The target (Spring Security 5.0.18.RELEASE) is not affected by CVE-2020-5408. The vulnerable queryableText() method that uses a fixed null initialization vector is deprecated with a security warning. This fix was shipped in the upstream Spring Security 5.0.18.RELEASE (committed by eleftheria.kousathana@gmail.com in f8f4d960b5) before TuxCare onboarded the version. The CVE affects versions 5.0.x...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2021-22119",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:34738da7-1175-5ff9-b9c8-f1eebd1e1274",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2021-22119 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. Spring Security 5.0.18.RELEASE is not affected by CVE-2021-22119. The vulnerable Map-based storage pattern that allows unbounded accumulation of OAuth2 authorization requests was introduced in later versions (5.2+) starting in March 2018. Version 5.0.18 uses the original safe implementation that stores only a single authorization request per session, which gets replaced on each new request, inherently preventing the resource exhaustion DoS attack.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2022-22976",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:7e647adb-717e-5067-be67-784e8c7cff1d",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2022-22976 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 The target Spring Security 5.0.18.RELEASE is NOT affected by CVE-2022-22976. The integer overflow vulnerability in BCrypt's rounds calculation (which causes zero salt rounds when log_rounds=31) was fixed in the upstream codebase in July 2012, long before this version was released. The fix (commit 14a5135ac3 by Joseph Walton) replaced the vulnerable `int rounds = 1 << log_rounds` with `long roun...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2022-22978",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:bffdac23-59dc-5055-b036-8879b5726adb",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2022-22978 is fixed in version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2022-31692",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:238046b6-59b6-5e21-b55a-d6eac4907399",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2022-31692 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. Prechecker: No vulnerable code from the fix was found; this version has none of the entry points of the fix's regression test and no class named after a file the fix changes. Version 5.0.18.RELEASE is on an older release line than any version the advisories list as affected. Advisories: GitHub GHSA-mmmh-wcxm-2wr4 (newer lines only), NVD (newer lines only).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2023-20862",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:80c5bc72-1a1f-5005-b8cc-2046bfc63a23",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2023-20862 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. This version configures the persistence filter before the logout filter (SecurityContextConfigurer.java:92, FilterComparator.java:70). Logout invokes its handlers before the success handler, and clears authentication and the holder even when session invalidation is disabled (LogoutFilter.java:109, SecurityContextLogoutHandler.java:70). The enclosing filter then saves the post-chain context in its finally block (SecurityContextPersistenceFilter.java:108). The repository snapshots the original authentication and explicitly removes the session attribute when the saved authentication is empty, so cleanup also works with serialized contexts without relying on mutation of the stored object (HttpSessionSecurityContextRepository.java:329, HttpSessionSecurityContextRepository.java:350).",
        "justification": "protected_at_runtime"
      }
    },
    {
      "id": "CVE-2024-22234",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:26f330b8-3f5f-509b-b9e1-b6debe182c42",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2024-22234 affects version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2024-22257",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:8bf5bfd8-ab66-55a5-a262-738be216a65a",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2024-22257 is fixed in version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2024-38810",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:9673227b-f95d-510a-af57-12edb68e20ee",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-38810 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.0.18.RELEASE is not affected by CVE-2024-38810. The vulnerability concerns the @AuthorizeReturnObject annotation, which does not exist in version 5.0.18.RELEASE. This annotation was first introduced in Spring Security 6.2.5 (March 2024) and the CVE specifically affects versions 6.3.0 and 6.3.1. Exhaustive searches of the codebase confirm the annotation is completely absent fro...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2024-38827",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:367128ea-ded1-5452-8ea3-8372f13b48ce",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2024-38827 affects version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2025-22223",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:8175393d-f278-55bf-9b6a-fea9380853ef",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-22223 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. Prechecker: no vulnerable code from the patch was found, and this version has none of the entry points of the fix's regression test and no class named after a file the fix changes. Advisories: GitHub, cve.org (VMware) and Snyk list only 6.4.0 to 6.4.3 as affected, so this version is older than the affected range; NVD gives no range. Confirmed not affected by the Java ELS team review on 2026-11-06.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-22234",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:72e67e18-b239-5202-a1b3-8bb30cbadab8",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-22234 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Version 5.0.18.RELEASE (HEAD: 94bc27ad36) does not contain the CVE-2025-22228 fix that introduced CVE-2025-22234. CVE-2025-22234 is a second-order vulnerability - a regression where the CVE-2025-22228 fix (adding a 72-byte password length check to BCrypt) inadvertently broke timing attack mitigation in DaoAuthenticationProvider. Since the CVE-2025-22228 fix is not present in this version, the r...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-41232",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:87920e59-459c-5333-8b11-064319c6a798",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-41232 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. CVE-2025-41232 is in UniqueSecurityAnnotationScanner, which Spring Security 6.4 added for method security in AspectJ mode. Spring Security 5.0.18.RELEASE does not contain that scanner, so it is not affected.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-41248",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:ad651c9d-99a0-568c-ae07-a0e2b0b6c525",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-41248 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. CVE-2025-41248 affects the annotation lookup used by @EnableMethodSecurity. Spring Security 5.0.18.RELEASE predates @EnableMethodSecurity, which was added in 5.6, and has no such lookup, so it is not affected.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-22746",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:14412e4c-6815-534e-aebe-8be82e491c74",
      "analysis": {
        "state": "resolved",
        "detail": "Vulnerability CVE-2026-22746 is fixed in version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2026-22751",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:462b6f3e-ead5-5ebc-8ad8-9e958ac15bef",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-22751 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.0.18.RELEASE is not affected by CVE-2026-22751. The vulnerable component (JdbcOneTimeTokenService and the entire One-Time Token authentication feature) does not exist in this version. The OTT feature was introduced in Spring Security 6.4.0 (July 2024), nearly 4 years after version 5.0.18.RELEASE was released (August 2020). The target repository contains no OTT-related code, cl...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-59276",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:8d51493c-92d0-552d-8cbd-533da5c779a1",
      "analysis": {
        "state": "exploitable",
        "detail": "Vulnerability CVE-2026-59276 affects version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core."
      }
    },
    {
      "id": "CVE-2026-59277",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
        }
      ],
      "bom-ref": "urn:uuid:a510a64c-2d98-50db-9c94-9248096e207a",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-59277 does not affect version 5.0.18.RELEASE-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.0.18.RELEASE does not contain the vulnerable InetAddressMatchers class. The CVE affects InetAddressMatchers.matchInternal() and matchExternal() builders, which classify IP addresses as internal/external based on address properties. This class was introduced in Spring Security 7.1, released years after the target version (5.0.18.RELEASE from August 2020). The target has a diffe...",
        "justification": "code_not_present"
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:maven/org.springframework.security/spring-security-core@5.0.18.RELEASE-tuxcare.1"
    }
  ]
}