{ "@id": "urn:uuid:2025add1-af3e-4aff-b136-05bad413ca00", "role": "Document Creator", "author": "https://tuxcare.com", "version": 35, "@context": "https://openvex.dev/ns/v0.2.0", "timestamp": "2026-11-03T12:42:49.066061+00:00", "statements": [ { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4" } } ], "timestamp": "2026-11-03T12:42:49.066061+00:00", "status_notes": "Vulnerability CVE-2021-22112 does not affect version 6.1.6-tuxcare.4 of org.springframework.security:spring-security-web. The target repository (Spring Security 6.1.6-tuxcare.9) is NOT AFFECTED by CVE-2021-22112. The vulnerability was fixed in the upstream Spring Security release before TuxCare onboarded version 6.1.6. The fix (commit 3116369f02 by Rob Winch) adds tracking of saveContext invocations via the isSaveContextInvoked flag, ensuring that SecurityContext changes are properly saved even when changed multiple times in a single request. This upstream fix is present in the target at HEAD (ddc661b43f).\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": "The target repository (Spring Security 6.1.6-tuxcare.9) is NOT AFFECTED by CVE-2021-22112. The vulnerability was fixed in the upstream Spring Security release before TuxCare onboarded version 6.1.6. The fix (commit 3116369f02 by Rob Winch) adds tracking of saveContext invocations via the isSaveContextInvoked flag, ensuring that SecurityContext changes are properly saved even when changed multiple times in a single request. This upstream fix is present in the target at HEAD (ddc661b43f).\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)." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4" } } ], "timestamp": "2026-11-03T12:18:14.184922+00:00", "status_notes": "Vulnerability CVE-2022-22978 does not affect version 6.1.6-tuxcare.4 of org.springframework.security:spring-security-web. CVE-2022-22978 is NOT present in Spring Security 6.1.6. The vulnerability concerns RegexRequestMatcher's handling of regex patterns containing `.` which, without the Pattern.DOTALL flag, would not match line terminators (\\n, \\r), allowing attackers to bypass authorization checks by injecting newline characters in request paths. The fix (adding Pattern.DOTALL) was already present in the upstream Spring Security release that TuxCare onboarded. Commit 472c25b5e8 by Rob Winch (May 12, 2022) introduced the fix, and this commit is an ancestor of the first TuxCare commit (1df57f122d \"Tuxcare setup for 6.1.6\"). The target code at web/src/main/java/org/springframework/security/web/util/matcher/RegexRequestMatcher.java:46-48,105 shows DEFAULT = Pattern.DOTALL is already applied.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.5.0, < 5.5.7; >= 5.6.0, < 5.6.4; < 5.4.11; >= 5.5.0, < 5.5.7; >= 5.6.0, < 5.6.4; < 5.4.11), NVD (< 5.5.7; >= 5.6.0, < 5.6.4), cve.org (>= 5.4, < 5.4.11; >= 5.5, < 5.5.7; >= 5.6, < 5.6.4), Snyk (< 5.4.11; >= 5.5.0, < 5.5.7; >= 5.6.0, < 5.6.4).", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2022-22978" }, "impact_statement": "CVE-2022-22978 is NOT present in Spring Security 6.1.6. The vulnerability concerns RegexRequestMatcher's handling of regex patterns containing `.` which, without the Pattern.DOTALL flag, would not match line terminators (\\n, \\r), allowing attackers to bypass authorization checks by injecting newline characters in request paths. The fix (adding Pattern.DOTALL) was already present in the upstream Spring Security release that TuxCare onboarded. Commit 472c25b5e8 by Rob Winch (May 12, 2022) introduced the fix, and this commit is an ancestor of the first TuxCare commit (1df57f122d \"Tuxcare setup for 6.1.6\"). The target code at web/src/main/java/org/springframework/security/web/util/matcher/RegexRequestMatcher.java:46-48,105 shows DEFAULT = Pattern.DOTALL is already applied.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 5.5.0, < 5.5.7; >= 5.6.0, < 5.6.4; < 5.4.11; >= 5.5.0, < 5.5.7; >= 5.6.0, < 5.6.4; < 5.4.11), NVD (< 5.5.7; >= 5.6.0, < 5.6.4), cve.org (>= 5.4, < 5.4.11; >= 5.5, < 5.5.7; >= 5.6, < 5.6.4), Snyk (< 5.4.11; >= 5.5.0, < 5.5.7; >= 5.6.0, < 5.6.4)." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2024-38821 is fixed in version 6.1.6-tuxcare.4 of org.springframework.security:spring-security-web.", "vulnerability": { "name": "CVE-2024-38821" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-22732 is fixed in version 6.1.6-tuxcare.4 of org.springframework.security:spring-security-web.", "vulnerability": { "name": "CVE-2026-22732" } }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-22747 affects version 6.1.6-tuxcare.4 of org.springframework.security:spring-security-web, and is fixed in 6.1.6-tuxcare.5.", "vulnerability": { "name": "CVE-2026-22747" }, "action_statement": "Vulnerability CVE-2026-22747 affects version 6.1.6-tuxcare.4 of org.springframework.security:spring-security-web, and is fixed in 6.1.6-tuxcare.5." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-22754 does not affect version 6.1.6-tuxcare.4 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 6.1.6. 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.1.6. The upstream POC tests (RegexMatcher, CiRegexMatcher + AuthorizationManager variants) were ported verbatim and pass." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4" } } ], "timestamp": "2026-10-15T15:58:00.121837+00:00", "status_notes": "Vulnerability CVE-2026-41706 affects version 6.1.6-tuxcare.4 of org.springframework.security:spring-security-web, and is fixed in 6.1.6-tuxcare.8.", "vulnerability": { "name": "CVE-2026-41706" }, "action_statement": "Vulnerability CVE-2026-41706 affects version 6.1.6-tuxcare.4 of org.springframework.security:spring-security-web, and is fixed in 6.1.6-tuxcare.8." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4" } } ], "timestamp": "2026-10-15T15:58:00.121837+00:00", "status_notes": "Vulnerability CVE-2026-47838 affects version 6.1.6-tuxcare.4 of org.springframework.security:spring-security-web, and is fixed in 6.1.6-tuxcare.8.", "vulnerability": { "name": "CVE-2026-47838" }, "action_statement": "Vulnerability CVE-2026-47838 affects version 6.1.6-tuxcare.4 of org.springframework.security:spring-security-web, and is fixed in 6.1.6-tuxcare.8." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4", "identifiers": { "purl": "pkg:maven/org.springframework.security/spring-security-web@6.1.6-tuxcare.4" } } ], "timestamp": "2026-10-30T12:34:56.763245+00:00", "status_notes": "Vulnerability CVE-2026-47841 does not affect version 6.1.6-tuxcare.4 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 6.1.6 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 6.1.6 contains no WebAuthn code, so it is not affected." } ] }