{
  "@id": "urn:uuid:f693204d-f8b9-4eef-9498-c417bde8dcc8",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 45,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-09T01:26:53.747840+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T21:03:35.301295+00:00",
      "status_notes": "Vulnerability CVE-2010-3700 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2010-3700 describes a path parameter bypass vulnerability in Spring Security 2.x before 2.0.6 and 3.x before 3.0.4. The target repository is Spring Security version 5.7.7. The upstream fix (SEC-1584, commit 7d97adc68789f4a191cee15de482530dd9d5c31d by Luke Taylor) that addresses this vulnerability is already present in the target version. The fix introduces HttpFirewall with RequestWrapper t...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2010-3700"
      },
      "impact_statement": "not_affected \u2014 CVE-2010-3700 describes a path parameter bypass vulnerability in Spring Security 2.x before 2.0.6 and 3.x before 3.0.4. The target repository is Spring Security version 5.7.7. The upstream fix (SEC-1584, commit 7d97adc68789f4a191cee15de482530dd9d5c31d by Luke Taylor) that addresses this vulnerability is already present in the target version. The fix introduces HttpFirewall with RequestWrapper t..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T19:38:00.213912+00:00",
      "status_notes": "Vulnerability CVE-2011-2731 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.7.7 is not affected by CVE-2011-2731. The vulnerability (race condition in RunAsManager causing privilege leakage through shared SecurityContext) was fixed in upstream commits SEC-1750 (2011-07-04) and SEC-1967 (2012-07-24), over 10 years before TuxCare onboarded version 5.7.7. The fixes create isolated SecurityContext instances for RunAs execution and ensure cleanup in finall...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2731"
      },
      "impact_statement": "not_affected \u2014 Spring Security 5.7.7 is not affected by CVE-2011-2731. The vulnerability (race condition in RunAsManager causing privilege leakage through shared SecurityContext) was fixed in upstream commits SEC-1750 (2011-07-04) and SEC-1967 (2012-07-24), over 10 years before TuxCare onboarded version 5.7.7. The fixes create isolated SecurityContext instances for RunAs execution and ensure cleanup in finall..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T23:15:39.919655+00:00",
      "status_notes": "Vulnerability CVE-2011-2732 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 The target Spring Security 5.7.7 is not affected by CVE-2011-2732 (CRLF injection in logout redirect). The vulnerability was fixed by upstream Spring Security through two commits that shipped in version 5.7.7 before TuxCare onboarding: (1) FirewalledResponse wrapper with CRLF validation on all redirects (commit 824464516c), and (2) targetUrlParameter defaulting to null, disabling parameter-base...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2732"
      },
      "impact_statement": "not_affected \u2014 The target Spring Security 5.7.7 is not affected by CVE-2011-2732 (CRLF injection in logout redirect). The vulnerability was fixed by upstream Spring Security through two commits that shipped in version 5.7.7 before TuxCare onboarding: (1) FirewalledResponse wrapper with CRLF validation on all redirects (commit 824464516c), and (2) targetUrlParameter defaulting to null, disabling parameter-base..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T22:53:14.279336+00:00",
      "status_notes": "Vulnerability CVE-2011-2894 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2011-2894 is NOT present in Spring Security 5.7.7-tuxcare.3. The vulnerability involved deserialization of untrusted SecurityContext objects in RMI remoting, allowing remote code execution via gadget chains. The upstream vendor (Luke Taylor, Spring Security) fixed this in 2011 (commit b48fc53fa2) by replacing SecurityContext serialization with String-only transmission of principal/credentia...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2011-2894"
      },
      "impact_statement": "not_affected \u2014 CVE-2011-2894 is NOT present in Spring Security 5.7.7-tuxcare.3. The vulnerability involved deserialization of untrusted SecurityContext objects in RMI remoting, allowing remote code execution via gadget chains. The upstream vendor (Luke Taylor, Spring Security) fixed this in 2011 (commit b48fc53fa2) by replacing SecurityContext serialization with String-only transmission of principal/credentia..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T21:21:33.020349+00:00",
      "status_notes": "Vulnerability CVE-2012-5055 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2012-5055 is NOT present in spring-security 5.7.7-tuxcare.3. The target contains the complete SEC-2056 timing attack mitigation introduced by upstream commit c076f0f2e190c73a17379d05935c2c81657adee9 (authored by Rob Winch at VMware). This fix was already present in the upstream Spring Security 5.7.7 release before TuxCare's onboarding. The DaoAuthenticationProvider.mitigateAgainstTimingAtta...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2012-5055"
      },
      "impact_statement": "not_affected \u2014 CVE-2012-5055 is NOT present in spring-security 5.7.7-tuxcare.3. The target contains the complete SEC-2056 timing attack mitigation introduced by upstream commit c076f0f2e190c73a17379d05935c2c81657adee9 (authored by Rob Winch at VMware). This fix was already present in the upstream Spring Security 5.7.7 release before TuxCare's onboarding. The DaoAuthenticationProvider.mitigateAgainstTimingAtta..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-29T07:42:31.773838+00:00",
      "status_notes": "Vulnerability CVE-2014-0097 affects version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core.",
      "vulnerability": {
        "name": "CVE-2014-0097"
      },
      "action_statement": "Vulnerability CVE-2014-0097 affects version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T17:45:45.570904+00:00",
      "status_notes": "Vulnerability CVE-2014-3527 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. The target repository (Spring Security 5.7.7-tuxcare.3) is NOT affected by CVE-2014-3527. The vulnerability involved CAS proxy ticket authentication using untrusted Host header values from HttpServletRequest to determine service identity, allowing an attacker to bypass access control restrictions between CAS services. The upstream fix (SEC-2688, commit 934937d9c1) was already present in Spring Security 5.7.7 when TuxCare onboarded it. All three affected files show the complete fix: DefaultServiceAuthenticationDetails uses the pre-configured casService parameter to derive protocol/host/port instead of HttpServletRequest values, ServiceAuthenticationDetailsSource passes serviceProperties.getService() to the constructor, and ServiceProperties always requires the service property. No vulnerable code paths exist, and no subsequent commits reverted the fix.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-3527"
      },
      "impact_statement": "The target repository (Spring Security 5.7.7-tuxcare.3) is NOT affected by CVE-2014-3527. The vulnerability involved CAS proxy ticket authentication using untrusted Host header values from HttpServletRequest to determine service identity, allowing an attacker to bypass access control restrictions between CAS services. The upstream fix (SEC-2688, commit 934937d9c1) was already present in Spring Security 5.7.7 when TuxCare onboarded it. All three affected files show the complete fix: DefaultServiceAuthenticationDetails uses the pre-configured casService parameter to derive protocol/host/port instead of HttpServletRequest values, ServiceAuthenticationDetailsSource passes serviceProperties.getService() to the constructor, and ServiceProperties always requires the service property. No vulnerable code paths exist, and no subsequent commits reverted the fix."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T12:38:41.778029+00:00",
      "status_notes": "Vulnerability CVE-2016-5007 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. CVE-2016-5007 is NOT present in Spring Security 5.7.7-tuxcare.3. Both fixes from the upstream patches are already integrated: (1) MvcRequestMatcher class uses Spring MVC's pattern matching for authorization rules, ensuring consistency with request routing; (2) DefaultHttpFirewall rejects URL-encoded slashes (%2f/%2F) by default. The fix commit e4c13e3c0e was authored by the upstream Spring Security team (rwinch@gopivotal.com) and was already included in the upstream 5.7.7 release before TuxCare onboarded it.\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": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-5007"
      },
      "impact_statement": "CVE-2016-5007 is NOT present in Spring Security 5.7.7-tuxcare.3. Both fixes from the upstream patches are already integrated: (1) MvcRequestMatcher class uses Spring MVC's pattern matching for authorization rules, ensuring consistency with request routing; (2) DefaultHttpFirewall rejects URL-encoded slashes (%2f/%2F) by default. The fix commit e4c13e3c0e was authored by the upstream Spring Security team (rwinch@gopivotal.com) and was already included in the upstream 5.7.7 release before TuxCare onboarded it.\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)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T12:14:20.152420+00:00",
      "status_notes": "Vulnerability CVE-2016-9879 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. Spring Security 5.7.7-tuxcare.3 is not affected by CVE-2016-9879. The vulnerability allowed bypassing security constraints via URL-encoded slashes (%2f/%2F) in request URIs on certain servlet containers. The fix was implemented upstream by Rob Winch (rwinch@gopivotal.com) in commit 666e356ebc and was already present in Spring Security 5.7.7 when TuxCare onboarded the release. The DefaultHttpFirewall.containsInvalidUrlEncodedSlash() method rejects requests containing encoded slashes by default, blocking the attack vector at the firewall layer before security constraint matching occurs.\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": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-9879"
      },
      "impact_statement": "Spring Security 5.7.7-tuxcare.3 is not affected by CVE-2016-9879. The vulnerability allowed bypassing security constraints via URL-encoded slashes (%2f/%2F) in request URIs on certain servlet containers. The fix was implemented upstream by Rob Winch (rwinch@gopivotal.com) in commit 666e356ebc and was already present in Spring Security 5.7.7 when TuxCare onboarded the release. The DefaultHttpFirewall.containsInvalidUrlEncodedSlash() method rejects requests containing encoded slashes by default, blocking the attack vector at the firewall layer before security constraint matching occurs.\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)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:14:29.621948+00:00",
      "status_notes": "Vulnerability CVE-2017-4995 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. The target repository (Spring Security 5.7.7-tuxcare.3) is not affected by CVE-2017-4995. The vulnerability was a Jackson deserialization issue in Spring Security 4.2.0-4.2.2 and 5.0.0.M1 where SecurityJackson2Modules.enableDefaultTyping() enabled unrestricted default typing, allowing arbitrary class instantiation during deserialization. The fix (commit 5dee8534cd by Rob Winch on May 31, 2017) introduced AllowlistTypeIdResolver that validates class names against a whitelist, explicit mixins, or Jackson annotations before deserialization. This fix was already present in the upstream Spring Security 5.7.7 release that TuxCare onboarded (commit 026929dd56 on the tuxcare-current branch). The vulnerable pattern (unrestricted class instantiation) is not present in the target version.\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": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-4995"
      },
      "impact_statement": "The target repository (Spring Security 5.7.7-tuxcare.3) is not affected by CVE-2017-4995. The vulnerability was a Jackson deserialization issue in Spring Security 4.2.0-4.2.2 and 5.0.0.M1 where SecurityJackson2Modules.enableDefaultTyping() enabled unrestricted default typing, allowing arbitrary class instantiation during deserialization. The fix (commit 5dee8534cd by Rob Winch on May 31, 2017) introduced AllowlistTypeIdResolver that validates class names against a whitelist, explicit mixins, or Jackson annotations before deserialization. This fix was already present in the upstream Spring Security 5.7.7 release that TuxCare onboarded (commit 026929dd56 on the tuxcare-current branch). The vulnerable pattern (unrestricted class instantiation) is not present in the target version.\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)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T16:48:47.972282+00:00",
      "status_notes": "Vulnerability CVE-2018-1199 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2018-1199 is not present in Spring Security 5.7.7. The vulnerability allowed attackers to bypass security constraints by adding URL path parameters with special encodings (semicolons). The fix, introduced by upstream in commit 0eef5b4b42 (Oct 2017), added StrictHttpFirewall which rejects requests containing semicolons (literal or URL-encoded) in URL paths. This fix was already present in th...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-1199"
      },
      "impact_statement": "not_affected \u2014 CVE-2018-1199 is not present in Spring Security 5.7.7. The vulnerability allowed attackers to bypass security constraints by adding URL path parameters with special encodings (semicolons). The fix, introduced by upstream in commit 0eef5b4b42 (Oct 2017), added StrictHttpFirewall which rejects requests containing semicolons (literal or URL-encoded) in URL paths. This fix was already present in th..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:14:29.621948+00:00",
      "status_notes": "Vulnerability CVE-2018-15801 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. CVE-2018-15801 is NOT present in Spring Security 5.7.7-tuxcare.3. The vulnerability was fixed in upstream Spring Security 5.1.2 (November 2018) by changing JWT issuer validation from URL object equality (which uses DNS resolution and could be bypassed) to string-based comparison. The target version 5.7.7 includes this upstream fix, which was committed by josh.cummings@gmail.com before TuxCare onboarded the release. The current code uses a refactored implementation with JwtClaimValidator that performs string comparison via issuer.equals(claimValue.toString()), achieving the same defense against the authorization bypass.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.1.0, < 5.1.2; >= 5.1.0, < 5.1.2), cve.org (>= 5.1.x, < 5.1.2), Snyk (>= 5.1.0, < 5.1.2.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-15801"
      },
      "impact_statement": "CVE-2018-15801 is NOT present in Spring Security 5.7.7-tuxcare.3. The vulnerability was fixed in upstream Spring Security 5.1.2 (November 2018) by changing JWT issuer validation from URL object equality (which uses DNS resolution and could be bypassed) to string-based comparison. The target version 5.7.7 includes this upstream fix, which was committed by josh.cummings@gmail.com before TuxCare onboarded the release. The current code uses a refactored implementation with JwtClaimValidator that performs string comparison via issuer.equals(claimValue.toString()), achieving the same defense against the authorization bypass.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.1.0, < 5.1.2; >= 5.1.0, < 5.1.2), cve.org (>= 5.1.x, < 5.1.2), Snyk (>= 5.1.0, < 5.1.2.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T12:26:45.505192+00:00",
      "status_notes": "Vulnerability CVE-2019-11272 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. Spring Security 5.7.7 is NOT AFFECTED by CVE-2019-11272. The vulnerable class PlaintextPasswordEncoder was removed entirely from Spring Security in upstream version 5.0.0.RC1 (October 2017), well before the target version 5.7.7 was released. The CVE describes a null-handling flaw in PlaintextPasswordEncoder.isPasswordValid() that allowed authentication with password \"null\" when a user had a null encoded password. Since this class does not exist in 5.7.7, the vulnerability pattern cannot manifest. The removal was performed by upstream (Rob Winch) and shipped in the upstream 5.7.7 release that TuxCare onboarded.\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": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-11272"
      },
      "impact_statement": "Spring Security 5.7.7 is NOT AFFECTED by CVE-2019-11272. The vulnerable class PlaintextPasswordEncoder was removed entirely from Spring Security in upstream version 5.0.0.RC1 (October 2017), well before the target version 5.7.7 was released. The CVE describes a null-handling flaw in PlaintextPasswordEncoder.isPasswordValid() that allowed authentication with password \"null\" when a user had a null encoded password. Since this class does not exist in 5.7.7, the vulnerability pattern cannot manifest. The removal was performed by upstream (Rob Winch) and shipped in the upstream 5.7.7 release that TuxCare onboarded.\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)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-02T23:56:59.714304+00:00",
      "status_notes": "Vulnerability CVE-2019-3795 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Target Spring Security 5.7.7-tuxcare.3 is NOT AFFECTED by CVE-2019-3795. The vulnerability (insecure randomness when using SecureRandomFactoryBean#setSeed) was fixed in upstream Spring Security prior to version 5.7.7. The vulnerable pattern (calling setSeed() before nextBytes()) is not present in the target code. The fix was authored by Josh Cummings (Spring Security team) in March 2019 and was...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-3795"
      },
      "impact_statement": "not_affected \u2014 Target Spring Security 5.7.7-tuxcare.3 is NOT AFFECTED by CVE-2019-3795. The vulnerability (insecure randomness when using SecureRandomFactoryBean#setSeed) was fixed in upstream Spring Security prior to version 5.7.7. The vulnerable pattern (calling setSeed() before nextBytes()) is not present in the target code. The fix was authored by Josh Cummings (Spring Security team) in March 2019 and was..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-06T18:39:00.080138+00:00",
      "status_notes": "Vulnerability CVE-2020-5407 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. Prechecker: An upstream release that contains the fix is part of this version's source history, and the code the fix removes is gone. Version 5.7.7 is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-48rw-j489-928m (affected up to 5.3.2), NVD (affected up to 5.3.2), CVE record (affected up to 5.3.2).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-5407"
      },
      "impact_statement": "Prechecker: An upstream release that contains the fix is part of this version's source history, and the code the fix removes is gone. Version 5.7.7 is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-48rw-j489-928m (affected up to 5.3.2), NVD (affected up to 5.3.2), CVE record (affected up to 5.3.2)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T22:11:36.730021+00:00",
      "status_notes": "Vulnerability CVE-2020-5408 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2020-5408 affects Spring Security versions prior to 5.3.2 (for 5.3.x branch). The target version 5.7.7 already contains the upstream fix applied in commit db155b30941536e6c33408a20f62e790b2c78a97 (April 2020) which deprecated the insecure Encryptors.queryableText() method with a clear security warning. This fix was shipped in the upstream release 5.7.7 that TuxCare onboarded, before any Tux...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-5408"
      },
      "impact_statement": "not_affected \u2014 CVE-2020-5408 affects Spring Security versions prior to 5.3.2 (for 5.3.x branch). The target version 5.7.7 already contains the upstream fix applied in commit db155b30941536e6c33408a20f62e790b2c78a97 (April 2020) which deprecated the insecure Encryptors.queryableText() method with a clear security warning. This fix was shipped in the upstream release 5.7.7 that TuxCare onboarded, before any Tux..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:12:34.459172+00:00",
      "status_notes": "Vulnerability CVE-2021-22119 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. The target repository (spring-security 5.7.7-tuxcare.3) is not affected by CVE-2021-22119. The fix for this DoS vulnerability was already present in the upstream release 5.7.7 that TuxCare onboarded. The vulnerable pattern (unbounded accumulation of OAuth2 authorization requests in session storage) has been removed by commit 35f5ebdbcf authored by the upstream Spring Security team.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.5.0, < 5.5.1; >= 5.4.0, < 5.4.7; >= 5.3.0, < 5.3.10; >= 5.2.0, < 5.2.11; >= 5.5.0, < 5.5.1; >= 5.4.0, < 5.4.7; >= 5.3.0, < 5.3.10; >= 5.2.0, < 5.2.11), NVD (>= 5.2.0, < 5.2.11; >= 5.3.0, < 5.3.10; >= 5.4.0, < 5.4.7; >= 5.5.0, < 5.5.1), cve.org (>= 5.5, < 5.5.1; >= 5.4, < 5.4.7; >= 5.3, < 5.3.10; < 5.2.x; < 5.2.11), Snyk (>= 5.5.0, < 5.5.1; >= 5.4.0, < 5.4.7; >= 5.3.0.RELEASE, < 5.3.10.RELEASE; >= 5.2.0.RELEASE, < 5.2.11.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22119"
      },
      "impact_statement": "The target repository (spring-security 5.7.7-tuxcare.3) is not affected by CVE-2021-22119. The fix for this DoS vulnerability was already present in the upstream release 5.7.7 that TuxCare onboarded. The vulnerable pattern (unbounded accumulation of OAuth2 authorization requests in session storage) has been removed by commit 35f5ebdbcf authored by the upstream Spring Security team.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.5.0, < 5.5.1; >= 5.4.0, < 5.4.7; >= 5.3.0, < 5.3.10; >= 5.2.0, < 5.2.11; >= 5.5.0, < 5.5.1; >= 5.4.0, < 5.4.7; >= 5.3.0, < 5.3.10; >= 5.2.0, < 5.2.11), NVD (>= 5.2.0, < 5.2.11; >= 5.3.0, < 5.3.10; >= 5.4.0, < 5.4.7; >= 5.5.0, < 5.5.1), cve.org (>= 5.5, < 5.5.1; >= 5.4, < 5.4.7; >= 5.3, < 5.3.10; < 5.2.x; < 5.2.11), Snyk (>= 5.5.0, < 5.5.1; >= 5.4.0, < 5.4.7; >= 5.3.0.RELEASE, < 5.3.10.RELEASE; >= 5.2.0.RELEASE, < 5.2.11.RELEASE)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T05:14:07.650164+00:00",
      "status_notes": "Vulnerability CVE-2022-22976 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 The target Spring Security 5.7.7 repository is NOT vulnerable to CVE-2022-22976 (BCrypt integer overflow). The vulnerability was fixed in the upstream release by commit 1229b27b87d30ae28a42ec2d4f598e146edc6d13 authored by Josh Cummings, which changed the rounds calculation from int to long and introduced the safe roundsForLogRounds() method to prevent integer overflow when log_rounds=31. This f...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-22976"
      },
      "impact_statement": "not_affected \u2014 The target Spring Security 5.7.7 repository is NOT vulnerable to CVE-2022-22976 (BCrypt integer overflow). The vulnerability was fixed in the upstream release by commit 1229b27b87d30ae28a42ec2d4f598e146edc6d13 authored by Josh Cummings, which changed the rounds calculation from int to long and introduced the safe roundsForLogRounds() method to prevent integer overflow when log_rounds=31. This f..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T12:19:18.164920+00:00",
      "status_notes": "Vulnerability CVE-2022-22978 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. Spring Security 5.7.7 is not affected by CVE-2022-22978 (RegexRequestMatcher authorization bypass). The upstream fix that adds Pattern.DOTALL to prevent regex bypass via line terminators was already included in the 5.7.7 release before TuxCare onboarded it. The vulnerable pattern (DEFAULT = 0) is not present; the fix (DEFAULT = Pattern.DOTALL) is present at RegexRequestMatcher.java line 46.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.5.0, < 5.5.7; >= 5.6.0, < 5.6.4; < 5.4.11; >= 5.5.0, < 5.5.7; >= 5.6.0, < 5.6.4; < 5.4.11), NVD (< 5.5.7; >= 5.6.0, < 5.6.4), cve.org (>= 5.4, < 5.4.11; >= 5.5, < 5.5.7; >= 5.6, < 5.6.4), Snyk (< 5.4.11; >= 5.5.0, < 5.5.7; >= 5.6.0, < 5.6.4).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-22978"
      },
      "impact_statement": "Spring Security 5.7.7 is not affected by CVE-2022-22978 (RegexRequestMatcher authorization bypass). The upstream fix that adds Pattern.DOTALL to prevent regex bypass via line terminators was already included in the 5.7.7 release before TuxCare onboarded it. The vulnerable pattern (DEFAULT = 0) is not present; the fix (DEFAULT = Pattern.DOTALL) is present at RegexRequestMatcher.java line 46.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.5.0, < 5.5.7; >= 5.6.0, < 5.6.4; < 5.4.11; >= 5.5.0, < 5.5.7; >= 5.6.0, < 5.6.4; < 5.4.11), NVD (< 5.5.7; >= 5.6.0, < 5.6.4), cve.org (>= 5.4, < 5.4.11; >= 5.5, < 5.5.7; >= 5.6, < 5.6.4), Snyk (< 5.4.11; >= 5.5.0, < 5.5.7; >= 5.6.0, < 5.6.4)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:10:25.284357+00:00",
      "status_notes": "Vulnerability CVE-2022-31692 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. The target Spring Security version 5.7.7 is NOT vulnerable to CVE-2022-31692. The vulnerability was fixed in upstream Spring Security 5.7.5, and the target version 5.7.7 already contains the complete fix. The AuthorizationFilter class properly extends GenericFilterBean (not the vulnerable OncePerRequestFilter) and includes all dispatcher type handling logic to prevent authorization bypass on FORWARD/INCLUDE requests. The fix commit (1f481aafff) by Marcus Da Coregio was shipped in the upstream release before TuxCare onboarded version 5.7.7.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.7.0, < 5.7.5; >= 5.6.0, < 5.6.9), NVD (>= 5.6.0, < 5.6.9; >= 5.7.0, < 5.7.5), Snyk (>= 5.6.0, < 5.6.9; >= 5.7.0, < 5.7.5).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2022-31692"
      },
      "impact_statement": "The target Spring Security version 5.7.7 is NOT vulnerable to CVE-2022-31692. The vulnerability was fixed in upstream Spring Security 5.7.5, and the target version 5.7.7 already contains the complete fix. The AuthorizationFilter class properly extends GenericFilterBean (not the vulnerable OncePerRequestFilter) and includes all dispatcher type handling logic to prevent authorization bypass on FORWARD/INCLUDE requests. The fix commit (1f481aafff) by Marcus Da Coregio was shipped in the upstream release before TuxCare onboarded version 5.7.7.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.7.0, < 5.7.5; >= 5.6.0, < 5.6.9), NVD (>= 5.6.0, < 5.6.9; >= 5.7.0, < 5.7.5), Snyk (>= 5.6.0, < 5.6.9; >= 5.7.0, < 5.7.5)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-07T13:34:00.146022+00:00",
      "status_notes": "Vulnerability CVE-2023-20862 affects version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core.",
      "vulnerability": {
        "name": "CVE-2023-20862"
      },
      "action_statement": "Vulnerability CVE-2023-20862 affects version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-29T01:28:06.753409+00:00",
      "status_notes": "Vulnerability CVE-2024-22234 affects version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core.",
      "vulnerability": {
        "name": "CVE-2024-22234"
      },
      "action_statement": "Vulnerability CVE-2024-22234 affects version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-07T13:54:00.182951+00:00",
      "status_notes": "Vulnerability CVE-2024-22257 is fixed in version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core.",
      "vulnerability": {
        "name": "CVE-2024-22257"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T16:52:51.215173+00:00",
      "status_notes": "Vulnerability CVE-2024-38810 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 CVE-2024-38810 affects Spring Security 6.3.0 and 6.3.1 due to missing authorization when using the @AuthorizeReturnObject annotation. The target repository (Spring Security 5.7.7-tuxcare.3) does not contain the @AuthorizeReturnObject annotation or any related code. This feature was introduced in Spring Security 6.3.0-RC1 (commit d169d5a835, 2024-03-15) and is not present in version 5.7.7. Since...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-38810"
      },
      "impact_statement": "not_affected \u2014 CVE-2024-38810 affects Spring Security 6.3.0 and 6.3.1 due to missing authorization when using the @AuthorizeReturnObject annotation. The target repository (Spring Security 5.7.7-tuxcare.3) does not contain the @AuthorizeReturnObject annotation or any related code. This feature was introduced in Spring Security 6.3.0-RC1 (commit d169d5a835, 2024-03-15) and is not present in version 5.7.7. Since..."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-07T13:54:00.182951+00:00",
      "status_notes": "Vulnerability CVE-2024-38827 is fixed in version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core.",
      "vulnerability": {
        "name": "CVE-2024-38827"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-09T01:26:53.747840+00:00",
      "status_notes": "Vulnerability CVE-2025-22223 affects version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core, and is fixed in 5.7.7-tuxcare.4.",
      "vulnerability": {
        "name": "CVE-2025-22223"
      },
      "action_statement": "Vulnerability CVE-2025-22223 affects version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core, and is fixed in 5.7.7-tuxcare.4."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-07T13:34:00.146022+00:00",
      "status_notes": "Vulnerability CVE-2025-22234 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.7.7 is not affected by CVE-2025-22234. This CVE is a secondary vulnerability introduced by the fix for CVE-2025-22228, which added a password length check to BCrypt that broke timing attack mitigation. The target version (5.7.7) never received the CVE-2025-22228 fix, and therefore does not contain the problematic code that causes CVE-2025-22234. The timing attack mitigation in...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2025-22234"
      },
      "impact_statement": "not_affected \u2014 Spring Security 5.7.7 is not affected by CVE-2025-22234. This CVE is a secondary vulnerability introduced by the fix for CVE-2025-22228, which added a password length check to BCrypt that broke timing attack mitigation. The target version (5.7.7) never received the CVE-2025-22228 fix, and therefore does not contain the problematic code that causes CVE-2025-22234. The timing attack mitigation in..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T10:47:42.736684+00:00",
      "status_notes": "Vulnerability CVE-2025-41232 does not affect version 5.7.7-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.7.7 does not contain that scanner, so it is not affected.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2025-41232"
      },
      "impact_statement": "CVE-2025-41232 is in UniqueSecurityAnnotationScanner, which Spring Security 6.4 added for method security in AspectJ mode. Spring Security 5.7.7 does not contain that scanner, so it is not affected."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T11:36:43.630807+00:00",
      "status_notes": "Vulnerability CVE-2025-41248 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. Spring Security 5.7.7 has no generic-type annotation matching of its own: method security looks annotations up through Spring Framework's annotation utilities, so the CVE-2025-41248 code is not present. The equivalent issue in Spring Framework is tracked as CVE-2025-41249.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2025-41248"
      },
      "impact_statement": "Spring Security 5.7.7 has no generic-type annotation matching of its own: method security looks annotations up through Spring Framework's annotation utilities, so the CVE-2025-41248 code is not present. The equivalent issue in Spring Framework is tracked as CVE-2025-41249."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-07T13:53:00.197276+00:00",
      "status_notes": "Vulnerability CVE-2026-22746 is fixed in version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core.",
      "vulnerability": {
        "name": "CVE-2026-22746"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-29T06:03:59.210364+00:00",
      "status_notes": "Vulnerability CVE-2026-22751 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.7.7 is not affected by CVE-2026-22751 because the vulnerable component (JdbcOneTimeTokenService) does not exist in this version. The One-Time Token (OTT) authentication feature was introduced in Spring Security 6.4.0, and version 5.7.7 predates this feature entirely. Comprehensive searches across the codebase found no JdbcOneTimeTokenService class, no OneTimeToken-related code...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-22751"
      },
      "impact_statement": "not_affected \u2014 Spring Security 5.7.7 is not affected by CVE-2026-22751 because the vulnerable component (JdbcOneTimeTokenService) does not exist in this version. The One-Time Token (OTT) authentication feature was introduced in Spring Security 6.4.0, and version 5.7.7 predates this feature entirely. Comprehensive searches across the codebase found no JdbcOneTimeTokenService class, no OneTimeToken-related code..."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-15T18:43:00.151252+00:00",
      "status_notes": "Vulnerability CVE-2026-59276 affects version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core, and is fixed in 5.7.7-tuxcare.2.",
      "vulnerability": {
        "name": "CVE-2026-59276"
      },
      "action_statement": "Vulnerability CVE-2026-59276 affects version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core, and is fixed in 5.7.7-tuxcare.2."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-core@5.7.7-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-29T10:38:18.047933+00:00",
      "status_notes": "Vulnerability CVE-2026-59277 does not affect version 5.7.7-tuxcare.1 of org.springframework.security:spring-security-core. not_affected \u2014 Spring Security 5.7.7 is not affected by CVE-2026-59277. The vulnerable component, the InetAddressMatchers utility class with matchInternal()/matchExternal() builders for classifying IP addresses as internal or external networks, does not exist in this version. The CVE describes a misclassification vulnerability where 0.0.0.0 and :: are incorrectly treated as external addresses. However, versio...",
      "justification": "vulnerable_code_not_in_execute_path",
      "vulnerability": {
        "name": "CVE-2026-59277"
      },
      "impact_statement": "not_affected \u2014 Spring Security 5.7.7 is not affected by CVE-2026-59277. The vulnerable component, the InetAddressMatchers utility class with matchInternal()/matchExternal() builders for classifying IP addresses as internal or external networks, does not exist in this version. The CVE describes a misclassification vulnerability where 0.0.0.0 and :: are incorrectly treated as external addresses. However, versio..."
    }
  ]
}