{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:6cefb492-a7fb-5d12-a43c-57e2e233cef2", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "spring-messaging", "purl": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6", "type": "library", "group": "org.springframework", "bom-ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6", "version": "5.1.20.RELEASE-tuxcare.6", "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2016-1000027", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:62eeabfd-3fcd-55c6-91b1-16347b915038", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2016-1000027 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging and will not be fixed. It is not a patchable flaw but an inherent risk of Java serialization. It is recommended not exposing HTTP Invoker endpoints to untrusted clients; if such exposure is absent, no further action is required", "response": [ "will_not_fix" ] } }, { "id": "CVE-2020-5421", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:10583720-03b1-58b0-a276-dbbde441616c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2020-5421 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2021-22096", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:a5d2ea04-ae4a-5de4-a0ae-e83228040496", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-22096 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2021-22118", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:df6ac896-2dfc-50ad-87d2-ba5a572e4796", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2021-22118 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22950", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:6e3b0a08-7cf2-5f39-bc3a-11dabaa36b7f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2022-22950 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22965", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:5e019009-9dea-51dd-876c-2d939e641ba8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2022-22965 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22968", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:4c9f1214-f927-5434-9bfd-0a39a1fb1098", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2022-22968 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22970", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:0b7ace00-950f-50d0-8c4e-e2472580d2af", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2022-22970 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2022-22971", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:46d47240-74d0-59c7-9e3d-2bec07e4dc5f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2022-22971 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2023-20861", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:499fa1d3-5f47-5aea-9e03-c73e44c20e48", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2023-20861 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2023-20863", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:5d3b0ab3-9b63-57c5-8dd1-243f5247ee2e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2023-20863 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-22243", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:c2284d66-9a6d-59f0-84f9-942490a0b3aa", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-22243 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-22259", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:3245f039-e8c9-57be-be1d-938cc046b03f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-22259 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-22262", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:9f2bba66-d594-5d9a-926d-3bea8da914f7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-22262 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-38808", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:e98c097d-f799-5cef-a99e-91eed12dd028", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38808 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-38809", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:605a6711-ba2f-5175-a0a8-514e77851297", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2024-38809 is a false positive for org.springframework:spring-messaging 5.1.20.RELEASE-tuxcare.6." } }, { "id": "CVE-2024-38816", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:1322ab66-d3d6-5c65-8e71-1dc2312e11e1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38816 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-38819", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:712e7b9b-16b5-50fa-8dca-946c85bc3201", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38819 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2024-38820", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:254f71bb-aa94-5c85-9c55-d4860249b9b1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2024-38820 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2025-22233", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:4f19382f-ed48-5c14-b9c1-66ac2f09ef39", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-22233 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2025-41242", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:6b84c0ba-8d28-58c9-a642-92363b6e982d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-41242 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2025-41249", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:66872ee8-535f-5d64-b8a1-4f7f2483a09a", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-41249 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2025-41254", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:e6da7474-df5d-5f40-8069-207c61649e86", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-41254 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-22735", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:02907d05-53c4-57d7-ab31-f7a7c7bd625d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22735 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-22737", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:37d5d570-e131-583d-9427-1864521d82ec", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22737 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-22740", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:716575aa-0207-5c22-968b-a8e1ec1d0833", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-22740 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-22741", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:b322a244-9e3f-540b-883d-068f868cb7fc", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22741 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-22745", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:f6ea838c-6a5a-5fb5-8676-a1588b2c9ded", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-22745 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41838", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:0f5d8d6e-e7bb-5c48-aa4c-e2fbab124219", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41838 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41839", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:faf327a9-ed98-5192-a35f-0e65b20c950d", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41839 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41840", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:b350c22d-fc40-56c7-8201-7ba86fecbb1b", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41840 does not affect version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging. not_affected \u2014 Spring Framework version 5.1.20.RELEASE-tuxcare.2 is NOT affected by CVE-2026-41840. The target predates the vulnerable architecture (PartGenerator/MultipartParser) introduced in Spring 5.3.0 and uses a fundamentally different multipart parsing implementation (Synchronoss NIO Multipart library).", "justification": "code_not_present" } }, { "id": "CVE-2026-41841", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:5c5029b9-7633-5ced-b32d-4ec4aa55ddda", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41841 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41842", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:1442f176-3f14-5faa-af75-4a485b9a0f1c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41842 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41843", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:eec6024a-e336-5820-9464-e4dff41033c8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41843 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41844", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:a42f1c88-ed20-5a7a-b645-60a1e982b98a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41844 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41845", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:79d92709-3c23-5630-b300-8d3689362d00", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41845 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41846", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:7112f0c3-a08a-5298-928e-322d8d6dc40c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41846 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41847", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:cd7bf16f-1bed-5533-97ab-2c72a6bb4e1c", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41847 does not affect version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging. Spring Framework 5.1.20.RELEASE is outside the CVE-2026-41847 affected range of 5.3.0 through 5.3.48 and predates the vulnerable RouterFunctionDsl.filter API." } }, { "id": "CVE-2026-41848", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:069b4c50-4181-5b3b-b8f8-2c23cec6d456", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41848 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41849", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:dba41d5a-f3a1-52f2-9d1a-b611c21e95f5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41849 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41850", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:ab89d046-982e-560d-a01f-01d7d1bda628", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41850 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41851", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:0bd64b39-bbe1-588f-a688-ee9d84cc19d9", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41851 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41852", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:54718ea1-a0a5-5fde-b1ff-ea1fbcfbbed2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41852 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41853", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:cd633e72-120b-52c6-afca-7e3b08e4b8d6", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-41853 does not affect version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging. not_affected \u2014 Spring Framework version 5.1.20 is not affected by CVE-2026-41853. The vulnerability affects versions 5.3.0 and later, where a new native multipart parser (DefaultPartHttpMessageReader) was introduced. Version 5.1.20 uses different multipart parsing implementations that do not contain the vulnerable code.", "justification": "code_not_present" } }, { "id": "CVE-2026-41854", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:6a3fd976-181a-5235-a8d2-65a5a5df6e53", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41854 affects version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-41855", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:a514579a-3491-5e98-9c46-56e8d135f874", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41855 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-47884", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:b7803e95-65d0-54d3-ae57-24b6b0ecbbad", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47884 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-47886", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:cc8a3168-791b-5a23-83f1-156744955671", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47886 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-47887", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:a8d9f0b9-dd3b-53e8-b0a9-35c3061f8f5c", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47887 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-47891", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:5bb79b8c-0946-52de-a1c8-0883e470945f", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47891 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-47893", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:c6f23f26-4e0b-594c-9459-81641d004cd5", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47893 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-59280", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:a4f9f0f4-d119-5003-8e2b-6eb09db624b1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59280 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-59281", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:b3575b3d-8049-51f9-bc90-a647de77f5d0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59281 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-59282", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:4de9c3e9-904a-55b6-85dd-3967398c5bbd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59282 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-59283", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:cd13aa6f-d907-5d5d-af6a-5e4f380d4424", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59283 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } }, { "id": "CVE-2026-59314", "affects": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ], "bom-ref": "urn:uuid:9174aa4b-b949-5cad-9b0c-7534e490e86a", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59314 is fixed in version 5.1.20.RELEASE-tuxcare.6 of org.springframework:spring-messaging." } } ], "dependencies": [ { "ref": "pkg:maven/org.springframework/spring-messaging@5.1.20.RELEASE-tuxcare.6" } ] }