{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:f237eeba-2346-56be-84a9-4281bc1a2a4d", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "spring-security-crypto", "purl": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1", "type": "library", "group": "org.springframework.security", "bom-ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1", "version": "5.8.14-tuxcare.1", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2007-1651", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:ff75a886-f06b-53ed-8747-c71c53f78d3f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2007-1651 does not affect version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto. 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-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:f4a0a0c0-7560-5438-9a5e-9eb1b4c73d40", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2007-1652 is a false positive for org.springframework.security:spring-security-crypto 5.8.14-tuxcare.1. 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-2018-1258", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:5353ae0d-96e6-5dad-aebc-428d8742c8a9", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2018-1258 does not affect version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto. CVE-2018-1258 affects Spring Framework's AspectJExpressionPointcut class, not Spring Security itself. The target (Spring Security 5.8.14) does not contain the vulnerable code - it exists only in the Spring Framework dependency. Spring Security 5.8.14 uses Spring Framework 5.3.39.tuxcare, which was released years after the fix (Spring Framework 5.0.7, June 2018) and contains the upstream patch. The vulnerable code pattern (annotation matching failure on proxy classes) is not present in Spring Security's codebase.", "justification": "requires_dependency" } }, { "id": "CVE-2020-5408", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:30459e04-86ff-5644-8a30-97a3002ea189", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2020-5408 does not affect version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto. not_affected \u2014 CVE-2020-5408 is not affecting this target. The vulnerability involves using a fixed null initialization vector (IV) in the queryable text encryptor, which enables dictionary attacks on encrypted data. The upstream vendor (Spring Security) applied their fix strategy by deprecating the vulnerable queryableText() method in commit db155b3094 (April 2020). This deprecation with security warning is ...", "justification": "code_not_present" } }, { "id": "CVE-2023-34042", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:04574b82-a75f-5042-b0cf-4298b37fdb39", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2023-34042 does not affect version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto. 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-2024-38821", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:d8d0921a-82e9-5e34-b6f6-64775252604b", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38821 is fixed in version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2024-38827", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:c7ee8587-e8bb-5e37-bca6-18ff2ef8d789", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38827 is fixed in version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2025-22228", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:3ce49e48-3fa0-51d5-91a1-ac9b82d23a87", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-22228 affects version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2025-22234", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:2dba5e77-271c-5a4f-a31e-9278d147a89c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-22234 affects version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2025-41248", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:5f52b4e6-f816-5d03-9e14-a1f391d76092", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2025-41248 does not affect version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto. Spring Security 5.8.14 is NOT AFFECTED by CVE-2025-41248. The vulnerable class UniqueSecurityAnnotationScanner does not exist in this version. The CVE describes an authorization bypass in Spring Security's annotation detection mechanism when using @EnableMethodSecurity with security annotations on methods in generic superclasses/interfaces with unbounded generics. However, this vulnerability was introduced in Spring Security 6.4.0 (August 2024) with the new UniqueSecurityAnnotationScanner class. Version 5.8.14 uses a fundamentally different annotation scanning mechanism (AnnotationUtils.findAnnotation from Spring Framework) that has been stable for years and does not have this generic type resolution bug. TuxCare applied the CVE fix only to version 6.4.3+ (commit 625768ebab), confirming 5.x versions are unaffected.", "justification": "code_not_present" } }, { "id": "CVE-2026-22732", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:e6c70aff-1733-5e43-9ce7-3b030106e52a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-22732 affects version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2026-22746", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:a16c824e-1be0-5590-bc2f-dc85efb2fffb", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22746 is fixed in version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2026-22747", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:35e9778b-9f67-5c9c-bc82-426c2258a52a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22747 is fixed in version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2026-22748", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:72830ad3-282f-54e9-b97d-2ed6de2066c2", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-22748 does not affect version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto. not_affected \u2014 Version 5.8.14 is not affected by CVE-2026-22748. The vulnerable code - the NimbusJwtDecoder.withIssuerLocation() and NimbusReactiveJwtDecoder.withIssuerLocation() builder methods without default issuer validation - was introduced in Spring Security 6.1.0 (April 2023), well after version 5.8.14. These builder methods do not exist in version 5.8.14. While 5.8.14 provides issuer-location-based co...", "justification": "code_not_present" } }, { "id": "CVE-2026-22753", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:19066d06-c71e-55d3-8ac1-1ea71102ca82", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-22753 does not affect version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto. 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-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:831f6bb5-3b65-50ef-837e-fba1296f1f80", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-22754 does not affect version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto. 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" } }, { "id": "CVE-2026-40988", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:9ab4cf66-ea80-56db-85b0-954c9d89ad84", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-40988 is fixed in version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2026-40993", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:0d56e9ca-ae4d-5d20-a325-27bb545816d8", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-40993 does not affect version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto. Spring Security 5.8.14 is not affected by CVE-2026-40993. The vulnerable component JdbcAssertingPartyMetadataRepository does not exist in this version. This class was introduced in Spring Security 7.0.0 (confirmed by @since 7.0 JavaDoc and upstream verification). The target version (5.8.14) predates this feature by multiple major releases. The JDBC-based SAML2 asserting party metadata storage with Java object deserialization capability that enables the vulnerability is entirely absent from the 5.8.14 codebase. Type A1 analysis (Rule 5): the INPUT (serialized Java objects in database columns verification_credentials and encryption_credentials) is not received anywhere because the input handler code path does not exist.", "justification": "code_not_present" } }, { "id": "CVE-2026-41003", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:19edf2c7-f0bf-56dc-8413-fc347c3d9dba", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41003 is fixed in version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2026-41694", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:45b8bb44-b99b-52f5-ba95-a94b9535f223", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41694 is fixed in version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2026-41706", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:be90c60c-bbb4-57d8-bd70-71b382dc018d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41706 is fixed in version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2026-47838", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:2281d268-cf5f-5a6b-bef4-473cf976e597", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-47838 affects version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2026-47842", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:d00a9150-609e-5285-8c61-1272a860c030", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-47842 affects version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2026-59270", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:b52af750-8084-5716-8f2b-5f3acc7d3ccb", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59270 affects version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } }, { "id": "CVE-2026-59276", "affects": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ], "bom-ref": "urn:uuid:9572471a-1cac-55a5-a433-e48842c60ccf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59276 affects version 5.8.14-tuxcare.1 of org.springframework.security:spring-security-crypto." } } ], "dependencies": [ { "ref": "pkg:maven/org.springframework.security/spring-security-crypto@5.8.14-tuxcare.1" } ] }