{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:36474c5d-1ec1-5c81-a721-6ad740ce628f", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "spring-messaging", "purl": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4", "type": "library", "group": "org.springframework", "bom-ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4", "version": "4.0.0.RELEASE-tuxcare.4", "pedigree": { "ancestors": [ { "name": "spring-messaging", "purl": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE", "type": "library", "group": "org.springframework", "version": "4.0.0.RELEASE" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2009-1190", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:35e4fccd-5c68-5fa2-af1a-0c2926418229", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2009-1190 does not affect version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging. not_affected \u2014 Spring Framework 4.0.0.RELEASE is not affected by CVE-2009-1190. While the Serializable regex pattern code still exists in AbstractRegexpMethodPointcut and JdkRegexpMethodPointcut, the underlying JDK vulnerability that this CVE exploits was fixed in JDK 1.6+. Spring Framework 4.0.0.RELEASE requires JDK 8 (with sourceCompatibility=1.6), making exploitation impossible. The CVE explicitly identifi...", "justification": "requires_environment" } }, { "id": "CVE-2011-2730", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:f9be5053-eaac-5487-b338-e6b18f7bd7f2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-2730 affects version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2011-2894", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:577ab82c-7960-569e-badf-ce7bf37a4a7f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-2894 affects version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2014-3578", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:36adb751-9ed7-5013-904b-ae5c7d1c134e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2014-3578 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2015-0201", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:84303ef1-2794-5ecd-93f2-5d4c6e78b488", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0201 affects version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2015-5211", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:53a18125-d601-522d-879d-cb55b9a3d97a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2015-5211 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2016-5007", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:a94b76c5-92b0-5be5-9840-6e531cf0f324", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2016-5007 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-11040", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:0f5b3b14-e638-55f7-9bfd-5f68f20eede5", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2018-11040 does not affect version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging. The vulnerable automatic JSONP handling in MappingJackson2JsonView was introduced in Spring Framework 4.1 and is not present in Spring Framework 4.0.0.RELEASE.", "justification": "code_not_present" } }, { "id": "CVE-2018-1199", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:d231a057-b519-5cfb-9b7e-cd538c0c170a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-1199 affects version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-1257", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:c0951a3b-3011-5bbb-82b5-5255f6e47258", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-1257 affects version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-1258", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:e8cfc347-9252-57cc-9d6c-e17184fa0aa7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-1258 affects version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-1270", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:a107ac18-f3de-5cdd-9d4c-904f1eda2eee", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2018-1270 does not affect version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging. The version is not vulnerable. [terminalized not_affected from patch_application_manual/not_vulnerable]", "justification": "code_not_present" } }, { "id": "CVE-2018-1271", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:0a2ca740-8b9c-5e11-931e-7dd40ec8b525", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2018-1271 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-1272", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:100424f2-d7d7-5d9c-ac51-47508ebec2e4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2018-1272 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-1275", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:542ae823-fcce-5169-a4d3-6c570c49f01f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2018-1275 does not affect version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging. Spring Framework 4.0.0.RELEASE is not affected by CVE-2018-1275. The vulnerability requires the SpEL-based selector feature for STOMP subscription filtering, which was introduced in version 4.2.0.RC1 (April 2015). Version 4.0.0 (released 2013) predates this feature entirely. Exhaustive searches confirm no selector expression evaluation code exists in the spring-messaging module.", "justification": "code_not_present" } }, { "id": "CVE-2018-15756", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:8544810e-dff8-57af-84d4-09d81056b9ee", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-15756 affects version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2021-22060", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:a572ec09-ddc7-5dc1-a9e6-eb316871c777", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-22060 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2021-22096", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:1ed98bd9-4d2f-5899-ac71-2e97494ccb0e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-22096 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22950", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:2b8e688d-3581-5966-8a5b-4179d2052490", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2022-22950 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22965", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:184b11bc-f7d5-5b28-965a-36436a8c36f5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2022-22965 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22968", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:f2a4f7f4-5a39-5ec0-8f99-d2e4fa597309", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2022-22968 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22970", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:f340aade-6b21-547a-8784-d701a6f06a84", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2022-22970 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22971", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:42cf6e63-b539-550e-a5c4-3d7c7e1b9166", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2022-22971 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2023-20861", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:4024304f-7bb6-574c-9449-0c476a3df92f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2023-20861 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2023-20863", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:acbb24e9-0db0-543d-af4c-d516cf39fd7c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2023-20863 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-22233", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:5075111b-345f-5f9d-9637-8ecfd94ca129", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-22233 affects version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-38808", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:932e5305-a55c-5643-b0c5-33903a1d082d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38808 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-38820", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:5db2f498-7089-56ac-93a2-c38092411468", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38820 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2025-22233", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:ce41c662-598f-54c5-8249-41bfa586d807", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-22233 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2025-41249", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:7bd48db0-7bdb-5ea9-b10d-8d46e698ec60", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-41249 affects version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-22740", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:7365c001-f9f7-55f7-921a-f3f50e92d712", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-22740 affects version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41848", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:a9f67c70-52a3-5e52-9429-c30c0d3b417c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41848 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41849", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:09457ead-4247-52a8-8064-3c14e6c580a4", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41849 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41850", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:5acac76d-ef76-5b2a-a53c-372e935ae77b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41850 affects version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging, and is fixed in 4.0.0.RELEASE-tuxcare.5." } }, { "id": "CVE-2026-41851", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:f5120fc1-d451-5091-be6c-8d21a1e370d3", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41851 does not affect version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging. not_affected \u2014 Spring Framework 4.0.0.RELEASE does not contain the vulnerability pattern described in CVE-2026-41851. The target version predates the introduction of pattern caching in SpEL's OperatorMatches (added January 2015), so the unbounded cache growth mechanism cannot occur. While the affected versions listed in the CVE start at 5.3.0, the vulnerability pattern itself (unbounded ConcurrentHashMap cach...", "justification": "code_not_present" } }, { "id": "CVE-2026-41852", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:3f0832a6-f78d-56eb-b8a2-7899b6b56558", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41852 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-47886", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:af46f61d-4fe5-51ff-ac8e-e6266eb0b3df", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47886 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-47888", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:63e33776-79bd-59f5-8a10-35304dfe7815", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-47888 does not affect version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging. CVE-2026-47888 is a memory leak in Spring Framework's RSocket support in spring-messaging, which was added in 5.2.0. Spring Framework 4.0.0.RELEASE contains no RSocket code, so it is not affected.", "justification": "code_not_present" } }, { "id": "CVE-2026-59282", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:a3224dd3-d153-5ec0-95a0-c900c7d105a8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59282 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-59283", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ], "bom-ref": "urn:uuid:1dab0d5f-d257-59fb-adb2-584fc02c8483", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59283 is fixed in version 4.0.0.RELEASE-tuxcare.4 of org.springframework:spring-messaging." } } ], "dependencies": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.0.0.RELEASE-tuxcare.4" } ] }