{
  "@id": "urn:uuid:c98318fd-9b7b-4730-a54e-615a244d2f8c",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 26,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-03T12:43:21.485909+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-bom@6.3.10-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-bom@6.3.10-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-03T12:43:21.485909+00:00",
      "status_notes": "Vulnerability CVE-2021-22112 does not affect version 6.3.10-tuxcare.4 of org.springframework.security:spring-security-bom. Spring Security 6.3.10 is NOT affected by CVE-2021-22112. The vulnerability fix was already included in the upstream Spring Security release. The fix (commit 3116369f02, January 2021) introduced the `isSaveContextInvoked` flag that ensures the final SecurityContext state is properly saved when the context is changed multiple times in a single request. This upstream fix predates the TuxCare initial setup commit (304f400bbf, April 2026) by over 5 years, confirming it shipped in the base upstream release.\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": "Spring Security 6.3.10 is NOT affected by CVE-2021-22112. The vulnerability fix was already included in the upstream Spring Security release. The fix (commit 3116369f02, January 2021) introduced the `isSaveContextInvoked` flag that ensures the final SecurityContext state is properly saved when the context is changed multiple times in a single request. This upstream fix predates the TuxCare initial setup commit (304f400bbf, April 2026) by over 5 years, confirming it shipped in the base upstream release.\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)."
    }
  ]
}