{ "@id": "urn:uuid:61bd65cd-ce9d-4b78-97fc-efaff3e805a3", "role": "Document Creator", "author": "https://tuxcare.com", "version": 31, "@context": "https://openvex.dev/ns/v0.2.0", "timestamp": "2026-11-04T09:07:59.808671+00:00", "statements": [ { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare" } } ], "timestamp": "2026-10-20T10:05:00.136501+00:00", "status_notes": "Vulnerability CVE-2007-1651 is a false positive for org.springframework.security:spring-security-config 5.7.11.tuxcare. direct vulnerability is in OpenID project", "vulnerability": { "name": "CVE-2007-1651" }, "impact_statement": "direct vulnerability is in OpenID project" }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare" } } ], "timestamp": "2026-10-20T10:05:00.136501+00:00", "status_notes": "Vulnerability CVE-2007-1652 is a false positive for org.springframework.security:spring-security-config 5.7.11.tuxcare. direct vulnerability is in OpenID project", "vulnerability": { "name": "CVE-2007-1652" }, "impact_statement": "direct vulnerability is in OpenID project" }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare" } } ], "timestamp": "2026-11-04T09:07:59.808671+00:00", "status_notes": "Vulnerability CVE-2023-34034 does not affect version 5.7.11.tuxcare of org.springframework.security:spring-security-config. The target Spring Security 5.7.11-tuxcare.11 is not affected by CVE-2023-34034. The upstream fix (commit 7813a9ba26) that ensures Spring Security and Spring WebFlux use consistent PathPatternParser instances with proper pattern normalization was already present in the upstream Spring Security 5.7.11 release that TuxCare onboarded. The vulnerable pattern matching mismatch does not exist in this version. The fix was authored by Marcus Da Coregio (upstream contributor) and shipped with the original 5.7.11 release before any TuxCare modifications.\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": "The target Spring Security 5.7.11-tuxcare.11 is not affected by CVE-2023-34034. The upstream fix (commit 7813a9ba26) that ensures Spring Security and Spring WebFlux use consistent PathPatternParser instances with proper pattern normalization was already present in the upstream Spring Security 5.7.11 release that TuxCare onboarded. The vulnerable pattern matching mismatch does not exist in this version. The fix was authored by Marcus Da Coregio (upstream contributor) and shipped with the original 5.7.11 release before any TuxCare modifications.\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": "affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare" } } ], "timestamp": "2026-10-29T07:31:18.734944+00:00", "status_notes": "Vulnerability CVE-2023-34035 affects version 5.7.11.tuxcare of org.springframework.security:spring-security-config.", "vulnerability": { "name": "CVE-2023-34035" }, "action_statement": "Vulnerability CVE-2023-34035 affects version 5.7.11.tuxcare of org.springframework.security:spring-security-config." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2023-34042 does not affect version 5.7.11.tuxcare of org.springframework.security:spring-security-config. Version 5.7.11 is not vulnerable to CVE-2023-34042. No backport is needed. The fix was included in Spring Security 5.7.11 by original developers, and version 5.7.11 is safe.", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2023-34042" }, "impact_statement": "Version 5.7.11 is not vulnerable to CVE-2023-34042. No backport is needed. The fix was included in Spring Security 5.7.11 by original developers, and version 5.7.11 is safe." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare" } } ], "timestamp": "2026-10-29T02:11:01.060172+00:00", "status_notes": "Vulnerability CVE-2025-22223 does not affect version 5.7.11.tuxcare of org.springframework.security:spring-security-config. not_affected \u2014 Spring Security 5.7.11 is NOT affected by CVE-2025-22223. The vulnerable class `UniqueSecurityAnnotationScanner` does not exist in this version - it was introduced in Spring Security 6.4.0 (August 2024). Version 5.7.11 uses a different annotation scanning mechanism based on Spring Framework's `AopUtils.getMostSpecificMethod()` and `AnnotationUtils.findAnnotation()`, which properly handles param...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2025-22223" }, "impact_statement": "not_affected \u2014 Spring Security 5.7.11 is NOT affected by CVE-2025-22223. The vulnerable class `UniqueSecurityAnnotationScanner` does not exist in this version - it was introduced in Spring Security 6.4.0 (August 2024). Version 5.7.11 uses a different annotation scanning mechanism based on Spring Framework's `AopUtils.getMostSpecificMethod()` and `AnnotationUtils.findAnnotation()`, which properly handles param..." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-22753 does not affect version 5.7.11.tuxcare 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 5.7.11.", "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 5.7.11." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.7.11.tuxcare" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-22754 does not affect version 5.7.11.tuxcare 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 5.7.11. 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 5.7.11. The upstream POC tests (RegexMatcher, CiRegexMatcher + AuthorizationManager variants) were ported verbatim and pass." } ] }