{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:5a33fc22-d545-5799-9898-48062b8f3722", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "spring-messaging", "purl": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1", "type": "library", "group": "org.springframework", "bom-ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1", "version": "4.3.26.RELEASE-tuxcare.1", "pedigree": { "ancestors": [ { "name": "spring-messaging", "purl": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE", "type": "library", "group": "org.springframework", "version": "4.3.26.RELEASE" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2009-1190", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:283e4f70-6eea-5366-8ec3-9c4c71a68010", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2009-1190 does not affect version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging. not_affected \u2014 CVE-2009-1190 is an algorithmic complexity vulnerability in Java's Pattern.compile method that affects \"JDK before 1.6\" when used with Spring Framework versions 1.1.0-2.5.6 and 3.0.0.M1-M2. The target version (Spring 4.3.26.RELEASE) is well beyond the affected Spring version range and requires JDK 8 to run (per README: \"JDK 8 update 20 or later\"). Since JDK 8 includes all fixes from JDK 1.6+, t...", "justification": "requires_environment" } }, { "id": "CVE-2011-2730", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:c09b27a5-ed56-564c-b445-6ff9e3b9b19b", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-2730 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2011-2894", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:ee7896b6-1224-5ca9-8115-2815e57b406d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2011-2894 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2014-3578", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:bb3877a9-004d-5244-8764-5ae184783142", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2014-3578 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2015-0201", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:17ad9537-965e-520f-b3d1-62f2d9a3531d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-0201 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2015-5211", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:c9a3d944-b608-513c-b33d-16e099cb5c83", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2015-5211 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2016-5007", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:499afb5e-6457-5edf-adf6-c6b8847deab3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-5007 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-11040", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:f7857e8a-9256-5193-bbd8-f6f294941020", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-11040 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-1199", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:f8ce241e-a7ca-5776-bd15-b9afdf3e49a1", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-1199 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-1257", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:0160a1f0-31b4-515a-8960-8249a0fd96ef", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2018-1257 does not affect version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging. not_affected \u2014 CVE-2018-1257 is NOT present in Spring Framework 4.3.26.RELEASE. The vulnerability affected versions prior to 4.3.17, and the fix was already included in the upstream 4.3.26.RELEASE that TuxCare onboarded. The fix (commit 246a6db1ca by Rossen Stoyanchev) allows administrators to disable selector header processing by setting selectorHeaderName to null, preventing ReDoS attacks via malicious Spri...", "justification": "code_not_present" } }, { "id": "CVE-2018-1258", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:9ccd6104-c36a-5a62-a2c6-669148143d0d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-1258 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-1270", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:a9fc2ab2-0cf9-5936-ad48-8506df3ab7fa", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-1270 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-1271", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:4975b8c3-f9d0-5d95-b0bc-59ac64cf5a88", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-1271 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-1272", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:9014d44e-f207-544a-ab6e-4ade553087b3", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-1272 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-1275", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:065b45b9-d86c-570c-9012-4d3764d89782", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-1275 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2018-15756", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:6544255c-db42-520f-8132-d2e127de34f0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2018-15756 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2021-22060", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:60d0771e-d45a-541e-9428-8ca48aab3e4f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-22060 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2021-22096", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:c4af6146-e7e2-5bad-8266-c5a83f584f4a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2021-22096 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22950", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:d9b71a2d-8ed4-5856-87b1-48c71490f834", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2022-22950 is fixed in version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22965", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:f43c4f57-7535-5b4e-adce-244e505500a7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-22965 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22968", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:62cf9ccf-3d88-5691-8dd0-937f63fe8381", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-22968 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging, and is fixed in 4.3.26.RELEASE-tuxcare.2." } }, { "id": "CVE-2022-22970", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:acb711db-f12c-5b9e-9c81-ff1dec3a31c2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-22970 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22971", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:5874c172-f952-577b-b3ba-3a9fbc3774df", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2022-22971 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging, and is fixed in 4.3.26.RELEASE-tuxcare.2." } }, { "id": "CVE-2023-20861", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:22ead070-2b30-527e-8aad-b6d6f9c6eec9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2023-20861 is fixed in version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2023-20863", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:1746f499-b04a-5951-afc1-25ad374397b0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-20863 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-22233", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:82857783-e207-5c4f-861d-046514f3881f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-22233 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-38808", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:2d849f91-83da-5b7b-bd26-25cbd11d4387", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38808 is fixed in version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-38820", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:e6d15737-2eec-53cb-aac9-157d8662868d", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-38820 does not affect version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging. not_affected \u2014 Version 4.3.26.RELEASE does not contain the vulnerable code pattern that CVE-2024-38820 fixes. This CVE specifically addresses locale-dependent String.toLowerCase() calls introduced by the CVE-2022-22968 fix. Since version 4.3.26 does not have the CVE-2022-22968 fix applied (which added toLowerCase() without Locale.ROOT), it cannot have the CVE-2024-38820 vulnerability. The target version uses ...", "justification": "code_not_present" } }, { "id": "CVE-2025-22233", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:8d9877de-0b1a-56dd-a8fc-489e335b5d8f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-22233 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2025-41249", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:59232f60-7019-5c90-91cf-3fedc52bb3d9", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-41249 is fixed in version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-22740", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:876c1563-b015-5331-9ee6-e79611373af4", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-22740 does not affect version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging. not_affected \u2014 Spring Framework 4.3.26.RELEASE is not affected by CVE-2026-22740. The vulnerability is specific to WebFlux reactive multipart handling, which was introduced in Spring Framework 5.0. Version 4.3.26.RELEASE uses traditional servlet-based synchronous multipart processing with proper cleanup mechanisms and does not contain the vulnerable reactive code path.", "justification": "code_not_reachable" } }, { "id": "CVE-2026-41848", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:d9fee305-bda8-5b6c-9eaa-a7a26aa88a79", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41848 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41849", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:3eb812a4-17b1-5043-a101-54576203814d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41849 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41850", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:6171ae31-719b-50b5-ab55-97e6fa12cf34", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41850 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41851", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:53b6ce13-b0b1-516c-a5ea-4b9ae08d7041", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41851 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41852", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:ade0e6b6-b76c-50bc-8e38-bf433396e2bc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41852 affects version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-47886", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:7036561b-7392-5f7d-ab3f-ae6c1de7c192", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47886 is fixed in version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-47888", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:7ec01c12-7350-52ca-8f7f-974d2c4fde4b", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-47888 does not affect version 4.3.26.RELEASE-tuxcare.1 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.3.26.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.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:20bcaec8-935a-5dd4-98be-c6a4d81b822a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59282 is fixed in version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-59283", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ], "bom-ref": "urn:uuid:e84eaaef-d4d3-5c75-ae9f-749a1f77e1f5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59283 is fixed in version 4.3.26.RELEASE-tuxcare.1 of org.springframework:spring-messaging." } } ], "dependencies": [ { "ref": "pkg:maven/org.springframework/spring-messaging@4.3.26.RELEASE-tuxcare.1" } ] }