{
  "@id": "urn:uuid:0c15f558-890a-42ea-b716-cccaceff9de6",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-09T19:13:13.380013+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-bom@6.0.7-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-bom@6.0.7-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-09T19:13:13.380013+00:00",
      "status_notes": "Vulnerability CVE-2021-22112 does not affect version 6.0.7-tuxcare.4 of org.springframework.security:spring-security-bom. CVE-2021-22112 is NOT present in Spring Security 6.0.7. The vulnerability\u2014failure to save SecurityContext when changed multiple times in a single request\u2014was fixed in upstream commit c72a6fac04 (2021-01-22) by adding an isSaveContextInvoked flag to ensure the final SecurityContext state is persisted. This fix was already present in the upstream Spring Security 6.0.7 release that TuxCare onboarded on 2026-09-14. The vulnerable code pattern does not exist in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.4.0, < 5.4.4; >= 5.3.0, < 5.3.8; < 5.2.9; >= 5.4.0, < 5.4.4; >= 5.3.0, < 5.3.8; < 5.2.9), NVD (< 5.2.9; >= 5.3.0, < 5.3.8; >= 5.4.0, < 5.4.4), cve.org (>= 5.4, < 5.4.4; >= 5.3, < 5.3.8.RELEASE; >= 5.2, < 5.2.9.RELEASE), Snyk (>= 5.4.0, < 5.4.4; >= 5.3.0.RELEASE, < 5.3.8.RELEASE; < 5.2.9.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-22112"
      },
      "impact_statement": "CVE-2021-22112 is NOT present in Spring Security 6.0.7. The vulnerability\u2014failure to save SecurityContext when changed multiple times in a single request\u2014was fixed in upstream commit c72a6fac04 (2021-01-22) by adding an isSaveContextInvoked flag to ensure the final SecurityContext state is persisted. This fix was already present in the upstream Spring Security 6.0.7 release that TuxCare onboarded on 2026-09-14. The vulnerable code pattern does not exist in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.4.0, < 5.4.4; >= 5.3.0, < 5.3.8; < 5.2.9; >= 5.4.0, < 5.4.4; >= 5.3.0, < 5.3.8; < 5.2.9), NVD (< 5.2.9; >= 5.3.0, < 5.3.8; >= 5.4.0, < 5.4.4), cve.org (>= 5.4, < 5.4.4; >= 5.3, < 5.3.8.RELEASE; >= 5.2, < 5.2.9.RELEASE), Snyk (>= 5.4.0, < 5.4.4; >= 5.3.0.RELEASE, < 5.3.8.RELEASE; < 5.2.9.RELEASE)."
    }
  ]
}