{
  "@id": "urn:uuid:e3e4274b-613a-4df2-97be-4d5d51aed78a",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-11T03:40:05.021795+00:00",
  "statements": [
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-crypto@5.5.7-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-crypto@5.5.7-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-11T03:40:05.021795+00:00",
      "status_notes": "Vulnerability CVE-2025-22228 is fixed in version 5.5.7-tuxcare.3 of org.springframework.security:spring-security-crypto.",
      "vulnerability": {
        "name": "CVE-2025-22228"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-crypto@5.5.7-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-crypto@5.5.7-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-11T03:40:05.021795+00:00",
      "status_notes": "Vulnerability CVE-2025-22234 does not affect version 5.5.7-tuxcare.3 of org.springframework.security:spring-security-crypto. not_affected \u2014 Not affected. CVE-2025-22234 is a regression introduced by the CVE-2025-22228 fix, which added a 72-byte password limit to BCrypt hashing. That limit made the password check fail early and broke the timing-attack mitigation in DaoAuthenticationProvider. This tree (5.5.7-tuxcare.1) has no such limit, so the regression is not present. The original timing mitigation is intact.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2025-22234"
      },
      "impact_statement": "not_affected \u2014 Not affected. CVE-2025-22234 is a regression introduced by the CVE-2025-22228 fix, which added a 72-byte password limit to BCrypt hashing. That limit made the password check fail early and broke the timing-attack mitigation in DaoAuthenticationProvider. This tree (5.5.7-tuxcare.1) has no such limit, so the regression is not present. The original timing mitigation is intact."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-crypto@5.5.7-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-crypto@5.5.7-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-11T03:40:05.021795+00:00",
      "status_notes": "Vulnerability CVE-2026-47842 is fixed in version 5.5.7-tuxcare.3 of org.springframework.security:spring-security-crypto.",
      "vulnerability": {
        "name": "CVE-2026-47842"
      }
    }
  ]
}