{ "@id": "urn:uuid:e741f110-662e-4164-9334-ec4be8851e98", "role": "Document Creator", "author": "https://tuxcare.com", "version": 32, "@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.8.16.tuxcare.3", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3" } } ], "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.8.16.tuxcare.3. 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.8.16.tuxcare.3", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2007-1652 is a false positive for org.springframework.security:spring-security-config 5.8.16.tuxcare.3. CVE-2007-1652 is a vulnerability in JanRain's myOpenID service, on the OpenID Provider side. The CVE record carries vendor and product \\\"n/a\\\" and a single version-unbounded CPE, cpe:2.3:a:openid:openid:*, and every reference points to JanRain's myOpenID security announcement of March 2007 and the openid.net security mailing list threads of the same month. The reported mechanism - a crafted web page that forcibly logs a user into an OpenID-enabled site, releases the user's personal information to it, and silently adds it to the user's trusted-sites list by way of a cached authentication token - consists entirely of decisions taken by an OpenID Provider. A relying party has no trusted-sites list and no auto-approval step at which the flaw could occur. The openid module of this library implements only the relying-party (consumer) role: OpenIDAuthenticationFilter drives the two-leg consumer flow and OpenID4JavaConsumer wraps openid4java's ConsumerManager. The tree contains no OpenID Provider implementation - no use of openid4java's server package or ServerManager - and no trusted-sites or auto-approval handling anywhere. Nor could this library have been affected when the issue was disclosed: the CVE was published on 24 March 2007, while the earliest OpenID code in the project dates from 20 April 2007 and only reached the shipped openid module in January 2008. The vulnerability therefore does not apply to this library in any version.", "vulnerability": { "name": "CVE-2007-1652" }, "impact_statement": "CVE-2007-1652 is a vulnerability in JanRain's myOpenID service, on the OpenID Provider side. The CVE record carries vendor and product \\\"n/a\\\" and a single version-unbounded CPE, cpe:2.3:a:openid:openid:*, and every reference points to JanRain's myOpenID security announcement of March 2007 and the openid.net security mailing list threads of the same month. The reported mechanism - a crafted web page that forcibly logs a user into an OpenID-enabled site, releases the user's personal information to it, and silently adds it to the user's trusted-sites list by way of a cached authentication token - consists entirely of decisions taken by an OpenID Provider. A relying party has no trusted-sites list and no auto-approval step at which the flaw could occur. The openid module of this library implements only the relying-party (consumer) role: OpenIDAuthenticationFilter drives the two-leg consumer flow and OpenID4JavaConsumer wraps openid4java's ConsumerManager. The tree contains no OpenID Provider implementation - no use of openid4java's server package or ServerManager - and no trusted-sites or auto-approval handling anywhere. Nor could this library have been affected when the issue was disclosed: the CVE was published on 24 March 2007, while the earliest OpenID code in the project dates from 20 April 2007 and only reached the shipped openid module in January 2008. The vulnerability therefore does not apply to this library in any version." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3" } } ], "timestamp": "2026-11-04T09:07:59.808671+00:00", "status_notes": "Vulnerability CVE-2023-34034 does not affect version 5.8.16.tuxcare.3 of org.springframework.security:spring-security-config. CVE-2023-34034 describes a pattern matching mismatch when using \"**\" in Spring Security WebFlux configuration that could lead to security bypass. The target repository (Spring Security 5.8.16-tuxcare.16) is NOT AFFECTED because the upstream fix commit 7813a9ba26 by Marcus Da Coregio was already present in the Spring Security 5.8.16 release that TuxCare onboarded. All four affected source files contain the complete fix: pattern normalization via initFullPathPattern() and consistent PathPatternParser usage. The fix dates to July 5, 2023, predating TuxCare's first commit (March 3, 2025), confirming this is an upstream fix shipped with the release.\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 describes a pattern matching mismatch when using \"**\" in Spring Security WebFlux configuration that could lead to security bypass. The target repository (Spring Security 5.8.16-tuxcare.16) is NOT AFFECTED because the upstream fix commit 7813a9ba26 by Marcus Da Coregio was already present in the Spring Security 5.8.16 release that TuxCare onboarded. All four affected source files contain the complete fix: pattern normalization via initFullPathPattern() and consistent PathPatternParser usage. The fix dates to July 5, 2023, predating TuxCare's first commit (March 3, 2025), confirming this is an upstream fix shipped with the release.\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@5.8.16.tuxcare.3", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3" } } ], "timestamp": "2026-10-20T10:05:00.136501+00:00", "status_notes": "Vulnerability CVE-2023-34035 is a false positive for org.springframework.security:spring-security-config 5.8.16.tuxcare.3. direct vulnerability is in Spring Security project - affected versions are 5.8.0-5.8.4 / 6.0.0-6.0.4 / 6.1.0-6.1.1, version 5.8.16 is not in this range", "vulnerability": { "name": "CVE-2023-34035" }, "impact_statement": "direct vulnerability is in Spring Security project - affected versions are 5.8.0-5.8.4 / 6.0.0-6.0.4 / 6.1.0-6.1.1, version 5.8.16 is not in this range" }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2023-34042 does not affect version 5.8.16.tuxcare.3 of org.springframework.security:spring-security-config. Version 5.8.16 is not vulnerable to CVE-2023-34042. No backport is needed. The fix was included in Spring Security 5.8.7, and version 5.8.16 already incorporates it.", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2023-34042" }, "impact_statement": "Version 5.8.16 is not vulnerable to CVE-2023-34042. No backport is needed. The fix was included in Spring Security 5.8.7, and version 5.8.16 already incorporates it." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3" } } ], "timestamp": "2026-10-29T02:07:12.200727+00:00", "status_notes": "Vulnerability CVE-2025-22223 does not affect version 5.8.16.tuxcare.3 of org.springframework.security:spring-security-config. not_affected \u2014 Target version 5.8.16 is NOT AFFECTED by CVE-2025-22223. The official Spring Security advisory explicitly lists only versions 6.4.0 through 6.4.3 as vulnerable. The vulnerable code (UniqueSecurityAnnotationScanner class) does not exist in 5.8.16 because it was introduced in version 6.4.0 (August 2024). Version 5.8.16 uses a different annotation scanning architecture based on Spring Framework's ...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2025-22223" }, "impact_statement": "not_affected \u2014 Target version 5.8.16 is NOT AFFECTED by CVE-2025-22223. The official Spring Security advisory explicitly lists only versions 6.4.0 through 6.4.3 as vulnerable. The vulnerable code (UniqueSecurityAnnotationScanner class) does not exist in 5.8.16 because it was introduced in version 6.4.0 (August 2024). Version 5.8.16 uses a different annotation scanning architecture based on Spring Framework's ..." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-22753 does not affect version 5.8.16.tuxcare.3 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.8.16.", "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.8.16." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-config@5.8.16.tuxcare.3" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-22754 does not affect version 5.8.16.tuxcare.3 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.8.16. 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.8.16. The upstream POC tests (RegexMatcher, CiRegexMatcher + AuthorizationManager variants) were ported verbatim and pass." } ] }