{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:ca8f79a7-8ce3-5bcb-a51c-e2aa50e1e3c9",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "spring-security-config",
      "purl": "pkg:maven/org.springframework.security/spring-security-config@5.8.14-tuxcare.4",
      "type": "library",
      "group": "org.springframework.security",
      "bom-ref": "pkg:maven/org.springframework.security/spring-security-config@5.8.14-tuxcare.4",
      "version": "5.8.14-tuxcare.4",
      "pedigree": {
        "ancestors": [
          {
            "name": "spring-security-config",
            "purl": "pkg:maven/org.springframework.security/spring-security-config@5.8.14",
            "type": "library",
            "group": "org.springframework.security",
            "version": "5.8.14"
          }
        ]
      },
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2007-1651",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-config@5.8.14-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:96d778f9-fe0b-5366-99a3-fe43ef18aa16",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2007-1651 does not affect version 5.8.14-tuxcare.4 of org.springframework.security:spring-security-config. not_affected \u2014 CVE-2007-1651 describes a CSRF vulnerability in OpenID implementations where cached DiscoveryInformation tokens persist in the HTTP session after logout, allowing session restoration attacks. The upstream Spring Security project fixed this vulnerability in commit f5468087c2 (April 2010) by adding session cleanup in the endConsumption method. The target repository (Spring Security 5.8.14.tuxcare...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2007-1652",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-config@5.8.14-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:789376cb-2c18-50ad-92fe-ca6852a8beeb",
      "analysis": {
        "state": "false_positive",
        "detail": "Vulnerability CVE-2007-1652 is a false positive for org.springframework.security:spring-security-config 5.8.14-tuxcare.4. CVE-2007-1652 is a vulnerability in JanRain's myOpenID hosted service, on the OpenID\nProvider side. It does not apply to Spring Security in any version.\n\nNo affected software product is on record. The CVE record carries vendor \"n/a\", product\n\"n/a\" and version \"n/a\"; NVD lists a single unversioned CPE, cpe:2.3:a:openid:openid:*,\nwith no version bounds; the GitHub advisory GHSA-3x88-xvgr-m6fg is unreviewed and lists\nno affected package in any ecosystem; OSV has no entry for any spring-security artifact\n(control: the same query returns 5 entries for spring-security-config and 31 for\nspring-security-core); and spring.io publishes no advisory for this CVE. Every one of the\neight references points to JanRain's myOpenID security-fix announcement of March 2007 or\nto the openid.net security mailing list threads of the same month, where the reporter\nstates the problem had to be fixed on the myOpenID server.\n\nThe reported mechanism is Provider-side by construction. A crafted web page uses a cached\nauthentication token and an existing Provider session to forcibly log a user into an\nOpenID-enabled site, release the user's personal information to it, and silently add that\nsite to the user's trusted-sites list. A trusted-sites auto-approval list exists only at\nan OpenID Provider; a relying party has no such list and no auto-approval step at which\nthe flaw could occur.\n\nThe openid module of Spring Security implements only the relying-party (consumer) role.\nOpenIDAuthenticationFilter drives the two-leg consumer flow and OpenID4JavaConsumer wraps\nopenid4java's ConsumerManager. The only openid4java packages referenced in the tree are\nconsumer, discovery, message and association - there is no use of org.openid4java.server,\nno ServerManager, no OpenID Provider implementation, and no trusted-sites or auto-approval\nhandling of any kind. No openid4java sources are vendored into the tree.\n\nNor could this library have been affected when the issue was disclosed: the CVE was\npublished on 24 March 2007, while the earliest OpenID code in the project dates from\n20 April 2007 and only reached the shipped openid module in January 2008.\n\nResolved consistently with spring-security 5.6.10 (VPV 9976), 5.7.11 (43741),\n5.7.12 (12031), 5.7.14 (40534) and 5.8.16 (330), all closed as false_positive."
      }
    },
    {
      "id": "CVE-2023-34034",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-config@5.8.14-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:7c1c42d7-5552-5052-8aa8-423960272d7b",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2023-34034 does not affect version 5.8.14-tuxcare.4 of org.springframework.security:spring-security-config. The target Spring Security 5.8.14 is not affected by CVE-2023-34034. The vulnerability concerns a pattern matching mismatch between Spring Security and Spring WebFlux when using \"**\" or other patterns in authorization rules. The fix (commit 7813a9ba26) was already present in the upstream Spring Security 5.8.14 release that TuxCare onboarded. All four affected files contain the proper fix: using PathPatternParser.defaultInstance with initFullPathPattern() normalization to ensure Security's matchers align with WebFlux's routing. The fix was authored by Marcus Da Coregio (upstream maintainer) and shipped in upstream versions 5.6.12, 5.7.10, and later, well before version 5.8.14.\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": "code_not_present"
      }
    },
    {
      "id": "CVE-2023-34035",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-config@5.8.14-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:6cf8a60f-bde3-5876-afcf-813cb3627b10",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2023-34035 does not affect version 5.8.14-tuxcare.4 of org.springframework.security:spring-security-config. Spring Security 5.8.14 is NOT affected by CVE-2023-34035. The vulnerability affected versions 5.8 prior to 5.8.5. The target version (5.8.14) contains upstream fixes (commits df239b6448 and 4ca54683ae) authored by Josh Cummings that implement runtime validation to prevent authorization rule misconfiguration in multi-servlet deployments. The fixes were already present in the upstream 5.8.14 release that TuxCare onboarded (first TuxCare commit 5b61a4c84b \"Onboard version 5.8.14\"). The implementation uses DeferredRequestMatcher with runtime servlet detection to either throw IllegalArgumentException for ambiguous configurations or dynamically select the correct matcher type per request.\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": "code_not_present"
      }
    },
    {
      "id": "CVE-2023-34042",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-config@5.8.14-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:26f6640a-f171-5223-8c0c-7a3091b7488f",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2023-34042 does not affect version 5.8.14-tuxcare.4 of org.springframework.security:spring-security-config. not_affected \u2014 The target Spring Security 5.8.14.tuxcare is not affected by CVE-2023-34042. The vulnerability involved a world-writable symlink (spring-security.xsd) that was packaged with incorrect file permissions. The upstream vendor (Spring Security) fixed this in version 5.7.11/5.8.7 by removing the symlink and implementing automated build-time generation using proper Java NIO operations that preserve co...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-22223",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-config@5.8.14-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:60b2c378-72f3-5636-9b3a-cdd70857338a",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-22223 does not affect version 5.8.14-tuxcare.4 of org.springframework.security:spring-security-config. not_affected \u2014 CVE-2025-22223 affects Spring Security's UniqueSecurityAnnotationScanner class introduced in version 6.4.0. Target version 5.8.14 uses a different annotation scanning implementation (AuthorizationAnnotationUtils with Spring Framework's AopUtils.getMostSpecificMethod) and does not contain the vulnerable code pattern. TuxCare backported this CVE only to version 6.4.3, confirming it does not affec...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-22753",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-config@5.8.14-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:ccf17241-29af-5a24-97bc-9aa41109b97f",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-22753 does not affect version 5.8.14-tuxcare.4 of org.springframework.security:spring-security-config. Spring Security 5.8.14 is not affected by CVE-2026-22753. The vulnerability is specific to PathPatternRequestMatcher.Builder functionality introduced in version 7.0.0. Version 5.8.14 uses a different request matching architecture (MvcRequestMatcher/AntPathRequestMatcher) that does not have the vulnerable code patterns. The CVE affects versions 7.0.0-7.0.4 only; 5.8.14 predates the introduction of PathPatternRequestMatcher entirely.",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2026-22754",
      "affects": [
        {
          "ref": "pkg:maven/org.springframework.security/spring-security-config@5.8.14-tuxcare.4"
        }
      ],
      "bom-ref": "urn:uuid:ce3f2488-558e-57d8-9b46-b3e6a67ef803",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2026-22754 does not affect version 5.8.14-tuxcare.4 of org.springframework.security:spring-security-config. Spring Security 5.8.14 is NOT affected by CVE-2026-22754. The vulnerability exists only in versions 7.0.0-7.0.4 and is specific to the PathPatternRequestMatcher architecture introduced in version 7.x. Version 5.8.14 uses the MvcRequestMatcher architecture which correctly handles servlet-path configuration through property injection and mutable builder patterns, with no builder return-value capture bug. The authorization bypass described in the CVE cannot occur in 5.8.14's architecture.",
        "justification": "code_not_reachable"
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:maven/org.springframework.security/spring-security-config@5.8.14-tuxcare.4"
    }
  ]
}