{
  "@id": "urn:uuid:658248bf-1df8-4ecf-8f18-2b7cea995a80",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 36,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-03T18:55:34.876883+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2007-1651 is a false positive for org.springframework.security:spring-security-web 5.6.10-tuxcare.2. False positive \u2014 OpenID CVE, not related to Spring Security. CVE-2007-1651 affects OpenID Provider application handling of cached \u201calways trust\u201d authorization. Spring Security is a relying-party consumer; its DISCOVERY_INFO_KEY cleanup only prevents reuse of local callback/discovery state and does not address the provider-side forced-login flaw. No upstream evidence identifies Spring Security as an affected product.",
      "vulnerability": {
        "name": "CVE-2007-1651"
      },
      "impact_statement": "False positive \u2014 OpenID CVE, not related to Spring Security. CVE-2007-1651 affects OpenID Provider application handling of cached \u201calways trust\u201d authorization. Spring Security is a relying-party consumer; its DISCOVERY_INFO_KEY cleanup only prevents reuse of local callback/discovery state and does not address the provider-side forced-login flaw. No upstream evidence identifies Spring Security as an affected product."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2"
          }
        }
      ],
      "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-web 5.6.10-tuxcare.2. CVE-2007-1652 is a vulnerability in JanRain's myOpenID hosted service, on the OpenID Provider side. NVD records it with vendor and product \\\"n/a\\\" behind a single unversioned CPE, cpe:2.3:a:openid:openid:*, and every reference points to JanRain's March 2007 myOpenID security-fix announcement and to the openid.net security mailing list of the same month, where the reporter states the problem had to be fixed on the myOpenID server. The reported mechanism - using cached tokens and an existing Provider session to forcibly log a user into a site, disclose their personal information to it, and add that site permanently to the user's trusted-sites list - is Provider-side behaviour; a trusted-sites auto-approval list exists only at the Provider and has no counterpart in a relying party. The corresponding GitHub advisory, GHSA-3x88-xvgr-m6fg, is unreviewed and lists no affected package in any ecosystem.The openid module of Spring Security implements only the relying-party (consumer) role. OpenIDConsumer and its single implementation OpenID4JavaConsumer wrap openid4java's ConsumerManager to begin and end a consumption, and OpenIDAuthenticationFilter together with OpenIDAuthenticationProvider turn the result into an Authentication. The only openid4java packages referenced anywhere in the source tree are consumer, discovery, message and association; there is no use of org.openid4java.server, no ServerManager, no OpenID Provider implementation, and no trusted-sites or \\\"always trust\\\" handling of any kind, nor are any openid4java sources vendored into the tree. Nor could the library have been affected when the issue was disclosed: the advisory was published in March 2007, while the earliest OpenID code in this project was contributed in April 2007 and the openid4java-based consumer only appeared in July 2007. The vulnerability therefore does not apply to Spring Security in any version, including 5.6.10.",
      "vulnerability": {
        "name": "CVE-2007-1652"
      },
      "impact_statement": "CVE-2007-1652 is a vulnerability in JanRain's myOpenID hosted service, on the OpenID Provider side. NVD records it with vendor and product \\\"n/a\\\" behind a single unversioned CPE, cpe:2.3:a:openid:openid:*, and every reference points to JanRain's March 2007 myOpenID security-fix announcement and to the openid.net security mailing list of the same month, where the reporter states the problem had to be fixed on the myOpenID server. The reported mechanism - using cached tokens and an existing Provider session to forcibly log a user into a site, disclose their personal information to it, and add that site permanently to the user's trusted-sites list - is Provider-side behaviour; a trusted-sites auto-approval list exists only at the Provider and has no counterpart in a relying party. The corresponding GitHub advisory, GHSA-3x88-xvgr-m6fg, is unreviewed and lists no affected package in any ecosystem.The openid module of Spring Security implements only the relying-party (consumer) role. OpenIDConsumer and its single implementation OpenID4JavaConsumer wrap openid4java's ConsumerManager to begin and end a consumption, and OpenIDAuthenticationFilter together with OpenIDAuthenticationProvider turn the result into an Authentication. The only openid4java packages referenced anywhere in the source tree are consumer, discovery, message and association; there is no use of org.openid4java.server, no ServerManager, no OpenID Provider implementation, and no trusted-sites or \\\"always trust\\\" handling of any kind, nor are any openid4java sources vendored into the tree. Nor could the library have been affected when the issue was disclosed: the advisory was published in March 2007, while the earliest OpenID code in this project was contributed in April 2007 and the openid4java-based consumer only appeared in July 2007. The vulnerability therefore does not apply to Spring Security in any version, including 5.6.10."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T12:42:09.520685+00:00",
      "status_notes": "Vulnerability CVE-2021-22112 does not affect version 5.6.10-tuxcare.2 of org.springframework.security:spring-security-web. CVE-2021-22112 is NOT present in Spring Security 5.6.10. The vulnerability allowed SecurityContext changes made multiple times in a single request to fail to save properly, potentially extending elevated privileges beyond their intended scope. The upstream fix (commit c72a6fac04) was already present in the Spring Security 5.6.10 release that TuxCare onboarded. The fix adds a boolean flag `isSaveContextInvoked` that ensures all subsequent SecurityContext modifications are saved to the HTTP session, not just the first one. The target code contains the complete fix implementation.\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": "CVE-2021-22112 is NOT present in Spring Security 5.6.10. The vulnerability allowed SecurityContext changes made multiple times in a single request to fail to save properly, potentially extending elevated privileges beyond their intended scope. The upstream fix (commit c72a6fac04) was already present in the Spring Security 5.6.10 release that TuxCare onboarded. The fix adds a boolean flag `isSaveContextInvoked` that ensures all subsequent SecurityContext modifications are saved to the HTTP session, not just the first one. The target code contains the complete fix implementation.\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@5.6.10-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T12:18:14.184922+00:00",
      "status_notes": "Vulnerability CVE-2022-22978 does not affect version 5.6.10-tuxcare.2 of org.springframework.security:spring-security-web. CVE-2022-22978 affects Spring Security RegexRequestMatcher when regex patterns using `.` (dot) don't include Pattern.DOTALL flag, allowing authorization bypass via newline characters in request paths. The fix (commit c6461d61ba from May 2022) changes DEFAULT from 0 to Pattern.DOTALL. Analysis confirms this fix is already present in the target repository at HEAD (6d428b8b71). The fix was shipped in upstream Spring Security 5.6.10 release before TuxCare's initial setup (commit 258ad9ee0d). Target version 5.6.10-tuxcare.10 inherits the fix from upstream - verdict is not_affected with upstream attribution.\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 affects Spring Security RegexRequestMatcher when regex patterns using `.` (dot) don't include Pattern.DOTALL flag, allowing authorization bypass via newline characters in request paths. The fix (commit c6461d61ba from May 2022) changes DEFAULT from 0 to Pattern.DOTALL. Analysis confirms this fix is already present in the target repository at HEAD (6d428b8b71). The fix was shipped in upstream Spring Security 5.6.10 release before TuxCare's initial setup (commit 258ad9ee0d). Target version 5.6.10-tuxcare.10 inherits the fix from upstream - verdict is not_affected with upstream attribution.\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@5.6.10-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2024-38821 is fixed in version 5.6.10-tuxcare.2 of org.springframework.security:spring-security-web.",
      "vulnerability": {
        "name": "CVE-2024-38821"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-22732 is fixed in version 5.6.10-tuxcare.2 of org.springframework.security:spring-security-web.",
      "vulnerability": {
        "name": "CVE-2026-22732"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-15T18:50:00.096707+00:00",
      "status_notes": "Vulnerability CVE-2026-22747 affects version 5.6.10-tuxcare.2 of org.springframework.security:spring-security-web, and is fixed in 5.6.10-tuxcare.8.",
      "vulnerability": {
        "name": "CVE-2026-22747"
      },
      "action_statement": "Vulnerability CVE-2026-22747 affects version 5.6.10-tuxcare.2 of org.springframework.security:spring-security-web, and is fixed in 5.6.10-tuxcare.8."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-22754 does not affect version 5.6.10-tuxcare.2 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 5.6.10. 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.6.10. 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@5.6.10-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2026-41706 affects version 5.6.10-tuxcare.2 of org.springframework.security:spring-security-web, and is fixed in 5.6.10-tuxcare.7.",
      "vulnerability": {
        "name": "CVE-2026-41706"
      },
      "action_statement": "Vulnerability CVE-2026-41706 affects version 5.6.10-tuxcare.2 of org.springframework.security:spring-security-web, and is fixed in 5.6.10-tuxcare.7."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T18:55:34.876883+00:00",
      "status_notes": "Vulnerability CVE-2026-47838 affects version 5.6.10-tuxcare.2 of org.springframework.security:spring-security-web, and is fixed in 5.6.10-tuxcare.11.",
      "vulnerability": {
        "name": "CVE-2026-47838"
      },
      "action_statement": "Vulnerability CVE-2026-47838 affects version 5.6.10-tuxcare.2 of org.springframework.security:spring-security-web, and is fixed in 5.6.10-tuxcare.11."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.security/spring-security-web@5.6.10-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-10-30T12:33:04.556385+00:00",
      "status_notes": "Vulnerability CVE-2026-47841 does not affect version 5.6.10-tuxcare.2 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 5.6.10 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 5.6.10 contains no WebAuthn code, so it is not affected."
    }
  ]
}