{
  "@id": "urn:uuid:5ad73dfd-2805-4fc0-b7e4-b08aa194975e",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 29,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T15:51:00.040518+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2007-1651 does not affect version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web. already_fixed \u2014 The target repository already contains the fix for CVE-2007-1651. The upstream patch commit f5468087c2 (April 15, 2010) that removes cached DiscoveryInformation from session is present in the target's git history, plus additional security enhancements from commit 89fa771093 (July 13, 2011) that add null checking and ATTRIBUTE_LIST_KEY removal.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2007-1651"
      },
      "impact_statement": "already_fixed \u2014 The target repository already contains the fix for CVE-2007-1651. The upstream patch commit f5468087c2 (April 15, 2010) that removes cached DiscoveryInformation from session is present in the target's git history, plus additional security enhancements from commit 89fa771093 (July 13, 2011) that add null checking and ATTRIBUTE_LIST_KEY removal."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2007-1652 does not affect version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web. already_fixed \u2014 The target repository (spring-security 5.7.11.tuxcare) already contains the security fixes for CVE-2007-1652. Both defensive measures from the upstream patches are present: (1) null check rejecting requests with missing DiscoveryInformation at lines 141-144, and (2) immediate session token removal at lines 149-150. These fixes were merged via upstream commits f5468087c2 (April 2010) and 89fa771...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2007-1652"
      },
      "impact_statement": "already_fixed \u2014 The target repository (spring-security 5.7.11.tuxcare) already contains the security fixes for CVE-2007-1652. Both defensive measures from the upstream patches are present: (1) null check rejecting requests with missing DiscoveryInformation at lines 141-144, and (2) immediate session token removal at lines 149-150. These fixes were merged via upstream commits f5468087c2 (April 2010) and 89fa771..."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2021-22112 is fixed in version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web.",
      "vulnerability": {
        "name": "CVE-2021-22112"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2022-22978 is fixed in version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web.",
      "vulnerability": {
        "name": "CVE-2022-22978"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2024-38821 does not affect version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web. Spring Security 4.2.12.RELEASE is NOT affected by CVE-2024-38821. This vulnerability specifically affects WebFlux applications (reactive/non-blocking Spring applications), but Spring Security 4.2.12 is built on Spring Framework 4.3.23, which predates WebFlux entirely. WebFlux was introduced in Spring Framework 5.0. The target version lacks the entire `org.springframework.security.web.server` package and all WebFlux-related code. The patch modifies `WebFilterChainProxy` and adds `ServerWebExchangeFirewall` - neither of which exist in this version. While this version does have firewall protection for SERVLET-based applications (HttpFirewall/StrictHttpFirewall in FilterChainProxy), it cannot process the CVE's required INPUT type (HTTP requests to WebFlux applications).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-38821"
      },
      "impact_statement": "Spring Security 4.2.12.RELEASE is NOT affected by CVE-2024-38821. This vulnerability specifically affects WebFlux applications (reactive/non-blocking Spring applications), but Spring Security 4.2.12 is built on Spring Framework 4.3.23, which predates WebFlux entirely. WebFlux was introduced in Spring Framework 5.0. The target version lacks the entire `org.springframework.security.web.server` package and all WebFlux-related code. The patch modifies `WebFilterChainProxy` and adds `ServerWebExchangeFirewall` - neither of which exist in this version. While this version does have firewall protection for SERVLET-based applications (HttpFirewall/StrictHttpFirewall in FilterChainProxy), it cannot process the CVE's required INPUT type (HTTP requests to WebFlux applications)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-22732 affects version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web.",
      "vulnerability": {
        "name": "CVE-2026-22732"
      },
      "action_statement": "Vulnerability CVE-2026-22732 affects version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-22747 affects version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web.",
      "vulnerability": {
        "name": "CVE-2026-22747"
      },
      "action_statement": "Vulnerability CVE-2026-22747 affects version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-22754 does not affect version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web. According to security advisories CVE-2026-22754 does not affect Spring-Security versions earlier than 7.0.0. This is supported by manual code inspection and proof-of-concept tests ported from the upstream fix commit. CVE-2026-22754 is an access-control bypass caused by PathPatternRequestMatcherFactoryBean.afterPropertiesSet() calling this.builder.basePath(this.basePath) and discarding the return value \u2014 PathPatternRequestMatcher.Builder is immutable/copy-on-modify, so the configured basePath was silently dropped and protected URLs (e.g., /spring/path) were left unmatched by the security filter chain. The vulnerability requires two pieces of infrastructure introduced in Spring Security 7.0.0: 1. The PathPatternRequestMatcher.Builder API (added in upstream commit 3e53cc2c4a, \"Use PathPatternRequestMatcher in config\"). 2. The PathPatternRequestMatcherFactoryBean class itself \u2014 the exact file patched by upstream commit 53bcf0d1 (the CVE fix). Neither piece exists in version 4.2.12.RELEASE. The upstream POC tests (RegexMatcher, CiRegexMatcher + AuthorizationManager variants) were ported verbatim and pass.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-22754"
      },
      "impact_statement": "According to security advisories CVE-2026-22754 does not affect Spring-Security versions earlier than 7.0.0. This is supported by manual code inspection and proof-of-concept tests ported from the upstream fix commit. CVE-2026-22754 is an access-control bypass caused by PathPatternRequestMatcherFactoryBean.afterPropertiesSet() calling this.builder.basePath(this.basePath) and discarding the return value \u2014 PathPatternRequestMatcher.Builder is immutable/copy-on-modify, so the configured basePath was silently dropped and protected URLs (e.g., /spring/path) were left unmatched by the security filter chain. The vulnerability requires two pieces of infrastructure introduced in Spring Security 7.0.0: 1. The PathPatternRequestMatcher.Builder API (added in upstream commit 3e53cc2c4a, \"Use PathPatternRequestMatcher in config\"). 2. The PathPatternRequestMatcherFactoryBean class itself \u2014 the exact file patched by upstream commit 53bcf0d1 (the CVE fix). Neither piece exists in version 4.2.12.RELEASE. The upstream POC tests (RegexMatcher, CiRegexMatcher + AuthorizationManager variants) were ported verbatim and pass."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-41706 does not affect version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web. not_affected \u2014 Spring Security version 4.2.12.RELEASE-tuxcare.1 is not affected by CVE-2026-41706. The vulnerable classes CookieRequestCache and CookieServerRequestCache do not exist in this version. This version uses HttpSessionRequestCache which stores redirect URLs in HTTP sessions (server-side), not in browser cookies, making the cookie-based open redirect attack vector impossible.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-41706"
      },
      "impact_statement": "not_affected \u2014 Spring Security version 4.2.12.RELEASE-tuxcare.1 is not affected by CVE-2026-41706. The vulnerable classes CookieRequestCache and CookieServerRequestCache do not exist in this version. This version uses HttpSessionRequestCache which stores redirect URLs in HTTP sessions (server-side), not in browser cookies, making the cookie-based open redirect attack vector impossible."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-47838 affects version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web.",
      "vulnerability": {
        "name": "CVE-2026-47838"
      },
      "action_statement": "Vulnerability CVE-2026-47838 affects version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@4.2.12.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-30T12:30:16.743106+00:00",
      "status_notes": "Vulnerability CVE-2026-47841 does not affect version 4.2.12.RELEASE-tuxcare.1 of org.springframework.security:spring-security-web. CVE-2026-47841 is in Spring Security's WebAuthn (passkeys) support, which was added in 6.4. Spring Security 4.2.12.RELEASE contains no WebAuthn code, so it is not affected.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-47841"
      },
      "impact_statement": "CVE-2026-47841 is in Spring Security's WebAuthn (passkeys) support, which was added in 6.4. Spring Security 4.2.12.RELEASE contains no WebAuthn code, so it is not affected."
    }
  ]
}
