{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:5ed49ce6-1719-5c69-8fa1-9d475c3d2be2", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2", "type": "library", "group": "io.netty", "name": "netty-resolver-dns", "version": "4.1.122.Final-tuxcare.2", "purl": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:f3b4a1b5-7b57-54bf-b978-fe3b081c4d61", "id": "CVE-2025-55163", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-55163 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:50611620-7d1e-596e-a6bc-5ccafba5837e", "id": "CVE-2025-58056", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-58056 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:867905f3-01bb-5e30-8661-c86da8201477", "id": "CVE-2025-58057", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-58057 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:69864924-ed3a-52f7-bd46-55ae3dfe3e35", "id": "CVE-2025-59419", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-59419 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e16fef4e-22e2-5187-b201-cd3e80832624", "id": "CVE-2025-67735", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-67735 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:29fbfe7f-3713-5723-8c9f-01d87d0db187", "id": "CVE-2026-33870", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33870 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e9e15bf1-38bc-5bc8-9aab-718af5aafda7", "id": "CVE-2026-33871", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33871 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:9f2c6399-2521-5df2-b223-aadfc09c4ca5", "id": "CVE-2026-41417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41417 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:ae788542-9952-5fb0-9cd4-ed3f0dd9880b", "id": "CVE-2026-42577", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-42577 does not affect version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns. CVE-2026-42577 affects Netty 4.2.x only (advisory range >= 4.2.0.Final, < 4.2.13.Final). An fd left registered with an epoll event mask of 0 is woken forever by the unmaskable EPOLLERR/EPOLLHUP after a RST on a half-closed connection. Target 4.1.122.Final is NOT affected due to architectural differences. The patch modifies EpollIoHandler.java and EpollIoOps.java, part of 4.2's IoHandler/IoOps abstraction. Neither file exists in 4.1.x, which registers via EpollEventLoop.modify() off AbstractEpollChannel.flags. That field is seeded Native.EPOLLET, and no read/close/half-close path clears it (only the explicit pre-registration setEpollMode(LEVEL_TRIGGERED) opt-in), so the registration stays edge-triggered and the RST is reported once per edge instead of on every epoll_wait. The chain from INPUT (connection state change) to GOAL (CPU busy-loop via empty event mask) is broken at step (ii): the target cannot produce an empty event mask. Verdict: not_affected. Justification: code_not_reachable (Rule 5 Type A2)." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:a5b11cf0-f6a0-5644-9d65-9d26a39a31ab", "id": "CVE-2026-42578", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42578 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:26f385c2-6089-53ca-8931-758521f31554", "id": "CVE-2026-42579", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42579 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c0a85d3a-0e0f-5264-8667-c1e4b98608c3", "id": "CVE-2026-42580", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42580 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:35d8e64e-3a4a-5ff2-9960-c1a04c4d635a", "id": "CVE-2026-42581", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42581 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:7b708548-bf87-574e-a344-f5b695fffe10", "id": "CVE-2026-42583", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42583 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:464bab29-4366-52ce-8424-f36803f1e8e7", "id": "CVE-2026-42584", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42584 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:088005f2-4d7d-58c7-ac70-84697ffd7009", "id": "CVE-2026-42585", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42585 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:3f487c67-1db4-5677-b589-2c9952ccb322", "id": "CVE-2026-42586", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42586 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e532ee8b-1cc5-5048-b761-a646c97577b4", "id": "CVE-2026-42587", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42587 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:da89d37e-ecab-53d8-98a6-819fd17144f2", "id": "CVE-2026-44248", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44248 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:55b6d9a5-0edd-568d-a914-561e3bc49535", "id": "CVE-2026-44249", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44249 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:976d31a5-bdd7-50ad-aeb6-96f65ccadc36", "id": "CVE-2026-44250", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44250 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f335ebbf-7b41-5abb-b48b-c45df1277529", "id": "CVE-2026-44890", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44890 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4165c694-b2dc-5494-9b3a-e24787dad93b", "id": "CVE-2026-44891", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44891 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:43a7ad4a-20a7-56a9-8abb-2715ff647d5b", "id": "CVE-2026-44893", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44893 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:2502cb3e-9506-5527-91e5-ae10e05f82bd", "id": "CVE-2026-45416", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-45416 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:9b71f564-a6e8-5a44-b4d3-431edce4f073", "id": "CVE-2026-45536", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-45536 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:edf72dd1-968b-5807-ab5b-6e9d7a3c7694", "id": "CVE-2026-45673", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-45673 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d69a6e93-a8e9-5220-be99-10ee773a3f90", "id": "CVE-2026-45674", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-45674 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:b17b6b5d-b153-53cb-a990-78860c358494", "id": "CVE-2026-46340", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46340 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:0b00d075-c17d-523d-9294-b2d0161946c3", "id": "CVE-2026-47244", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47244 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:a3466a87-90a6-5b4c-94e9-a1fa96ff2a29", "id": "CVE-2026-47691", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47691 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:80cb77ff-a2fc-54a5-aa83-eed8f89030a3", "id": "CVE-2026-48006", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48006 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:083ab9c1-4882-5c9b-b802-fe49de9350e8", "id": "CVE-2026-48043", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48043 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:be5dc8c7-11c5-5da1-a555-0183a5892ec1", "id": "CVE-2026-48059", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48059 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4e16776a-308e-5eb0-9a64-41edca00a331", "id": "CVE-2026-50010", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50010 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f09e811c-a110-5dd5-9a0a-69be5e740dbb", "id": "CVE-2026-50011", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50011 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:92c79e9c-4095-5620-a5d1-a5904170e034", "id": "CVE-2026-50020", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50020 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e592f7cf-a20e-5e99-a342-e23b2dc2d6dc", "id": "CVE-2026-50560", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50560 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:efcca03e-9f07-571f-b668-9b052dde655b", "id": "CVE-2026-55831", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-55831 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:5c244c68-3b45-59c9-bdc2-4a714ea73e73", "id": "CVE-2026-55833", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-55833 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:ca5d62c9-afd9-5ad4-82a4-29dc5e7705af", "id": "CVE-2026-55851", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-55851 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:ed9b0bc4-249f-5dea-8f61-3cb2098df7d1", "id": "CVE-2026-56745", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56745 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:29b6c649-3b32-56be-92cf-0ccddcea90c6", "id": "CVE-2026-56746", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56746 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:fb98a8ff-59e1-51c9-a2a7-d41efe4aed22", "id": "CVE-2026-56817", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56817 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:eb8cef43-cddc-5957-a844-2b6883e6b606", "id": "CVE-2026-56818", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56818 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:8db974fc-8b90-5d36-95fb-a1d53c524f3f", "id": "CVE-2026-56819", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56819 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:2b5b5808-76af-5df3-a71d-e6d4ca1fd05f", "id": "CVE-2026-56820", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56820 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:9b14af54-a95b-5e12-921a-0bc61613ba41", "id": "CVE-2026-56821", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56821 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4f1c4768-0679-50e3-83c5-a7dcee6df127", "id": "CVE-2026-56822", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56822 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:786e1925-8fe5-5278-bc6f-8cfd7745ae2e", "id": "CVE-2026-59898", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59898 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4a4e729a-7831-5dfc-af18-5a9a2108e045", "id": "CVE-2026-59899", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59899 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:844a33b4-7b64-5511-a18e-ade6286c289f", "id": "CVE-2026-59900", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59900 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:3ec51a61-2b26-55df-ac9a-3ee546645281", "id": "CVE-2026-59901", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59901 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:63b08958-effe-5705-828a-7c16cc5574e3", "id": "CVE-2026-59902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59902 affects version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f72d8e64-017e-56be-b060-0e579c40caf3", "id": "CVE-2026-59903", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59903 affects version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e50a4398-9377-59de-a046-9371a8645330", "id": "CVE-2026-59919", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59919 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:330b3162-024b-5c88-a0f4-41bd6d43bbe5", "id": "CVE-2026-59920", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59920 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4a5739b6-fd60-5e88-b313-e599933ca447", "id": "CVE-2026-59921", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59921 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:5662f2c1-a075-5ecd-8ab7-f1d6f28ea5c2", "id": "CVE-2026-73507", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-73507 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:a2a91aab-b635-5df6-b854-c375abfbf042", "id": "CVE-2026-73508", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-73508 is fixed in version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:0bb0a66b-24e4-506d-8cd3-25fcfbec18de", "id": "GHSA-mfg7-5gfp-c4w3", "analysis": { "state": "exploitable", "detail": "Vulnerability GHSA-mfg7-5gfp-c4w3 affects version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:79f4190e-6330-5601-a7b1-2e787f7f672f", "id": "GHSA-v74w-7mr3-4qg3", "analysis": { "state": "exploitable", "detail": "Vulnerability GHSA-v74w-7mr3-4qg3 affects version 4.1.122.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.2" } ] }