{
  "@id": "urn:uuid:e22a1a32-55d7-4293-90d0-4eb65d6e850d",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 32,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-04T09:14:29.621948+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@6.2.2-tuxcare.9",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@6.2.2-tuxcare.9"
          }
        }
      ],
      "timestamp": "2026-11-04T09:10:25.284357+00:00",
      "status_notes": "Vulnerability CVE-2023-34034 does not affect version 6.2.2-tuxcare.9 of org.springframework.security:spring-security-config. CVE-2023-34034: The target version 6.2.2-tuxcare.9 is NOT AFFECTED. The vulnerability (pattern interpretation mismatch between Spring Security and Spring WebFlux when using \"**\" patterns) was fixed in upstream commit 7813a9ba26 on 2023-07-05, which predates the upstream 6.2.2 release (2024-02-16). The fix is present in all four affected source files, ensuring patterns are parsed using initFullPathPattern() with the default PathPatternParser instance, eliminating the security bypass risk. This is an upstream fix authored by marcusdacoregio@gmail.com, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.6.0, < 5.6.12; >= 5.7.0, < 5.7.10; >= 5.8.0, < 5.8.5; >= 6.0.0, < 6.0.5; >= 6.1.0, < 6.1.2), NVD (>= 5.6.0, < 5.6.12; >= 5.7.0, < 5.7.10; >= 5.8.0, < 5.8.5; >= 6.0.0, < 6.0.5; >= 6.1.0, < 6.1.2), cve.org (>= 6.1.0, <= 6.1.1; >= 6.0.0, <= 6.0.4; >= 5.8.0, <= 5.8.4; >= 5.7.0, <= 5.7.9; >= 5.6.0, <= 5.6.11), Snyk (>= 5.6.0, < 5.6.12; >= 5.7.0, < 5.7.10; >= 5.8.0, < 5.8.5; >= 6.0.0, < 6.0.5; >= 6.1.0, < 6.1.2).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-34034"
      },
      "impact_statement": "CVE-2023-34034: The target version 6.2.2-tuxcare.9 is NOT AFFECTED. The vulnerability (pattern interpretation mismatch between Spring Security and Spring WebFlux when using \"**\" patterns) was fixed in upstream commit 7813a9ba26 on 2023-07-05, which predates the upstream 6.2.2 release (2024-02-16). The fix is present in all four affected source files, ensuring patterns are parsed using initFullPathPattern() with the default PathPatternParser instance, eliminating the security bypass risk. This is an upstream fix authored by marcusdacoregio@gmail.com, not a TuxCare backport.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.6.0, < 5.6.12; >= 5.7.0, < 5.7.10; >= 5.8.0, < 5.8.5; >= 6.0.0, < 6.0.5; >= 6.1.0, < 6.1.2), NVD (>= 5.6.0, < 5.6.12; >= 5.7.0, < 5.7.10; >= 5.8.0, < 5.8.5; >= 6.0.0, < 6.0.5; >= 6.1.0, < 6.1.2), cve.org (>= 6.1.0, <= 6.1.1; >= 6.0.0, <= 6.0.4; >= 5.8.0, <= 5.8.4; >= 5.7.0, <= 5.7.9; >= 5.6.0, <= 5.6.11), Snyk (>= 5.6.0, < 5.6.12; >= 5.7.0, < 5.7.10; >= 5.8.0, < 5.8.5; >= 6.0.0, < 6.0.5; >= 6.1.0, < 6.1.2)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@6.2.2-tuxcare.9",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@6.2.2-tuxcare.9"
          }
        }
      ],
      "timestamp": "2026-11-04T09:14:29.621948+00:00",
      "status_notes": "Vulnerability CVE-2023-34035 does not affect version 6.2.2-tuxcare.9 of org.springframework.security:spring-security-config. Spring Security 6.2.2 is NOT affected by CVE-2023-34035. The vulnerability affects versions 5.8 prior to 5.8.5, 6.0 prior to 6.0.5, and 6.1 prior to 6.1.2. Version 6.2.2 is beyond these affected ranges. The upstream fix (commit df239b6448 by Josh Cummings, dated 2023-07-05) was already included in the Spring Security 6.2.2 release that TuxCare onboarded. The vulnerable code pattern (automatically choosing MVC matchers based solely on classpath presence without servlet configuration validation) is not present. The target contains the complete defense logic that detects ambiguous multi-servlet configurations and throws IllegalArgumentException to force explicit matcher disambiguation.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.8.0, < 5.8.5; >= 6.0.0, < 6.0.5; >= 6.1.0, < 6.1.2), NVD (>= 5.8.0, < 5.8.5; >= 6.0.0, < 6.0.5; >= 6.1.0, < 6.1.2), cve.org (>= 5.8.0, <= 5.8.4; >= 6.0.0, <= 6.0.4; >= 6.1.0, <= 6.1.1), Snyk (>= 5.8.0, < 5.8.5; >= 6.0.0, < 6.0.5; >= 6.1.0, < 6.1.2).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-34035"
      },
      "impact_statement": "Spring Security 6.2.2 is NOT affected by CVE-2023-34035. The vulnerability affects versions 5.8 prior to 5.8.5, 6.0 prior to 6.0.5, and 6.1 prior to 6.1.2. Version 6.2.2 is beyond these affected ranges. The upstream fix (commit df239b6448 by Josh Cummings, dated 2023-07-05) was already included in the Spring Security 6.2.2 release that TuxCare onboarded. The vulnerable code pattern (automatically choosing MVC matchers based solely on classpath presence without servlet configuration validation) is not present. The target contains the complete defense logic that detects ambiguous multi-servlet configurations and throws IllegalArgumentException to force explicit matcher disambiguation.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.8.0, < 5.8.5; >= 6.0.0, < 6.0.5; >= 6.1.0, < 6.1.2), NVD (>= 5.8.0, < 5.8.5; >= 6.0.0, < 6.0.5; >= 6.1.0, < 6.1.2), cve.org (>= 5.8.0, <= 5.8.4; >= 6.0.0, <= 6.0.4; >= 6.1.0, <= 6.1.1), Snyk (>= 5.8.0, < 5.8.5; >= 6.0.0, < 6.0.5; >= 6.1.0, < 6.1.2)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@6.2.2-tuxcare.9",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@6.2.2-tuxcare.9"
          }
        }
      ],
      "timestamp": "2026-11-03T14:39:17.858992+00:00",
      "status_notes": "Vulnerability CVE-2023-34042 does not affect version 6.2.2-tuxcare.9 of org.springframework.security:spring-security-config. not_affected \u2014 The target Spring Security 6.2.2-tuxcare.9 is not affected by CVE-2023-34042. The vulnerability (a world-writable spring-security.xsd file caused by a symlink in the source tree) was fixed by upstream Spring Security in commit 5b293d2116 on 2023-09-14, authored by Rob Winch. This fix was already present in the upstream release before TuxCare onboarded version 6.2.2 on 2026-04-03. The vulnerable...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-34042"
      },
      "impact_statement": "not_affected \u2014 The target Spring Security 6.2.2-tuxcare.9 is not affected by CVE-2023-34042. The vulnerability (a world-writable spring-security.xsd file caused by a symlink in the source tree) was fixed by upstream Spring Security in commit 5b293d2116 on 2023-09-14, authored by Rob Winch. This fix was already present in the upstream release before TuxCare onboarded version 6.2.2 on 2026-04-03. The vulnerable..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@6.2.2-tuxcare.9",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@6.2.2-tuxcare.9"
          }
        }
      ],
      "timestamp": "2026-10-29T02:23:11.597840+00:00",
      "status_notes": "Vulnerability CVE-2025-22223 does not affect version 6.2.2-tuxcare.9 of org.springframework.security:spring-security-config. not_affected \u2014 Spring Security 6.2.2 is NOT affected by CVE-2025-22223. The vulnerable code (UniqueSecurityAnnotationScanner) was introduced in version 6.4.0-M4 (July 2024) and does not exist in 6.2.2. Version 6.2.2 uses Spring Framework's MergedAnnotations API with TYPE_HIERARCHY search strategy, which correctly resolves annotations on parameterized type hierarchies. The CVE fix was only backported to 6.4.3,...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2025-22223"
      },
      "impact_statement": "not_affected \u2014 Spring Security 6.2.2 is NOT affected by CVE-2025-22223. The vulnerable code (UniqueSecurityAnnotationScanner) was introduced in version 6.4.0-M4 (July 2024) and does not exist in 6.2.2. Version 6.2.2 uses Spring Framework's MergedAnnotations API with TYPE_HIERARCHY search strategy, which correctly resolves annotations on parameterized type hierarchies. The CVE fix was only backported to 6.4.3,..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@6.2.2-tuxcare.9",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@6.2.2-tuxcare.9"
          }
        }
      ],
      "timestamp": "2026-10-27T10:26:52.870157+00:00",
      "status_notes": "Vulnerability CVE-2026-22753 does not affect version 6.2.2-tuxcare.9 of org.springframework.security:spring-security-config. According to security advisories CVE-2026-22753 does not affect Spring-Security versions earlier than 7.0.0. This is supported by manual code inspection. CVE-2026-22753 is an access-control bypass that occurs when a user-registered PathPatternRequestMatcher.Builder bean (configured with a basePath/servlet path prefix) is silently ignored by the securityMatchers DSL, causing the security filter chain to match a different URL than the user configured. The vulnerability requires two pieces of infrastructure introduced in Spring Security 7.0.0: 1. The PathPatternRequestMatcher.Builder API itself (added in upstream commit aeb2dbc2 on 2025-08-18). 2. The wiring in HttpSecurityConfiguration.createSharedObjects() that registers this Builder as a shared object \u2014 the exact line patched by upstream commit 438c783c (the CVE fix). Neither piece exists in version 6.2.2.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-22753"
      },
      "impact_statement": "According to security advisories CVE-2026-22753 does not affect Spring-Security versions earlier than 7.0.0. This is supported by manual code inspection. CVE-2026-22753 is an access-control bypass that occurs when a user-registered PathPatternRequestMatcher.Builder bean (configured with a basePath/servlet path prefix) is silently ignored by the securityMatchers DSL, causing the security filter chain to match a different URL than the user configured. The vulnerability requires two pieces of infrastructure introduced in Spring Security 7.0.0: 1. The PathPatternRequestMatcher.Builder API itself (added in upstream commit aeb2dbc2 on 2025-08-18). 2. The wiring in HttpSecurityConfiguration.createSharedObjects() that registers this Builder as a shared object \u2014 the exact line patched by upstream commit 438c783c (the CVE fix). Neither piece exists in version 6.2.2."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-config@6.2.2-tuxcare.9",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-config@6.2.2-tuxcare.9"
          }
        }
      ],
      "timestamp": "2026-10-27T10:26:52.870157+00:00",
      "status_notes": "Vulnerability CVE-2026-22754 does not affect version 6.2.2-tuxcare.9 of org.springframework.security:spring-security-config. 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 6.2.2. 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 6.2.2. The upstream POC tests (RegexMatcher, CiRegexMatcher + AuthorizationManager variants) were ported verbatim and pass."
    }
  ]
}