{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:68dcd0fa-d63f-5ef3-bf4c-cad3bac8876f", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1", "type": "library", "group": "io.netty", "name": "netty-codec-dns", "version": "4.1.122.Final-tuxcare.1", "purl": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:8f006e0a-2ccb-575a-9861-56def3b7b83f", "id": "CVE-2025-55163", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-55163 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:94cb4867-cd74-5eca-9b98-2d8d22dcb77c", "id": "CVE-2025-58056", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-58056 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:c605f595-5d4e-57ad-8f94-d6e562c1bf8d", "id": "CVE-2025-58057", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-58057 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:b6fde8ca-4815-55a1-bb14-8407afd35e30", "id": "CVE-2025-59419", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59419 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:c5d3230e-1816-5d8e-9a0a-e3ef8f75e3af", "id": "CVE-2025-67735", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-67735 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:6da0c563-813e-57f3-af49-b2cc16ce2f78", "id": "CVE-2026-33870", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33870 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:87841b8d-5a88-5a19-9460-761528021f82", "id": "CVE-2026-33871", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33871 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:3a9fe0bc-7357-52a2-b0e6-abe091163b94", "id": "CVE-2026-41417", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41417 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:3e612db1-642f-539b-8bd0-c44511a93580", "id": "CVE-2026-42577", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-42577 does not affect version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-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-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:96d9cc30-00b3-5c4d-b5d2-bc3249c65de2", "id": "CVE-2026-42578", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42578 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:09bf327f-7f5c-55bf-8964-37b783a46cbd", "id": "CVE-2026-42579", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42579 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:80cd7363-6e2e-5645-b095-038047125657", "id": "CVE-2026-42580", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42580 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:77e8b4dc-4779-515c-9f30-ce58c80478de", "id": "CVE-2026-42581", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42581 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:af394442-c1ab-5cb7-afd8-929570851063", "id": "CVE-2026-42583", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42583 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:85f00aa4-4068-56ef-9e4b-cab674c618d0", "id": "CVE-2026-42584", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42584 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:2c995172-99ea-52b6-bce4-21572845e214", "id": "CVE-2026-42585", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42585 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:9b61971a-33a6-55d8-a889-16b4b097e06e", "id": "CVE-2026-42586", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42586 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:42d93685-5e7d-5a28-9c03-811c6f4aaf0e", "id": "CVE-2026-42587", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42587 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:c80b1a34-3e0f-5dd4-ae52-c2e38256dfbb", "id": "CVE-2026-44248", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44248 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:36effd04-6e2a-5bc6-bb23-3fa754c7fea4", "id": "CVE-2026-44249", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44249 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:3f2ec69c-e913-5c69-af56-b407be20c23e", "id": "CVE-2026-44250", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44250 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:cbdd864c-84c4-5057-b4b0-6b13c89c35f4", "id": "CVE-2026-44890", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44890 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:68a58630-382d-5e88-b424-cb4539556bec", "id": "CVE-2026-44891", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44891 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:d8eb7906-4cff-5cc2-951d-0c64987243a2", "id": "CVE-2026-44893", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44893 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:23f68d72-0ce2-5d74-80b7-dfad5dbb21a6", "id": "CVE-2026-45416", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45416 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:81a3c3ae-5de2-5ced-8b79-de516d6c40a1", "id": "CVE-2026-45536", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45536 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:1b19bcb2-ed36-5f52-b184-da78d18d6569", "id": "CVE-2026-45673", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45673 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:21a916e6-0c23-59e5-9171-5145ede7464f", "id": "CVE-2026-45674", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45674 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:ef3b60de-8f28-5b42-ba25-188699ced49b", "id": "CVE-2026-46340", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-46340 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:6e4457ef-f2cb-5c6f-a12d-4a2f2f77dc8f", "id": "CVE-2026-47244", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-47244 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:5d16d779-bc18-5052-a23c-5c4313b48eb3", "id": "CVE-2026-47691", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-47691 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:fc6f499b-5b49-5352-9e92-d51c278422d9", "id": "CVE-2026-48006", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-48006 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:dc302768-239c-5daa-91c8-e27315fa617a", "id": "CVE-2026-48043", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-48043 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:b3602ae8-5ae3-5705-9d36-22452857afa8", "id": "CVE-2026-48059", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-48059 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:1ab42f1d-e0b3-5761-bd0c-a7f00e2766d9", "id": "CVE-2026-50010", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50010 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:791f03d5-1f7e-52b9-8a11-0c2495013d22", "id": "CVE-2026-50011", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50011 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:bac0aad1-27d3-5699-aa34-f4f6c5c1d247", "id": "CVE-2026-50020", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50020 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:518e350c-e671-5167-8594-b3f3aa652253", "id": "CVE-2026-50560", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50560 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:e26e09ab-b2d1-56bb-a948-f4f8f6d0e9ef", "id": "CVE-2026-55831", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55831 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:47d17c8a-d920-5bad-b842-779feaeb2156", "id": "CVE-2026-55833", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55833 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:f9e9720c-b615-5116-91df-23deea577af7", "id": "CVE-2026-55851", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55851 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:46fc2d9e-711d-5739-92d9-49fceb0d9824", "id": "CVE-2026-56745", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56745 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:0db26c0b-b239-5e20-8780-dc11d63781be", "id": "CVE-2026-56746", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56746 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:5da00719-a8df-5508-ba84-5b74c7709259", "id": "CVE-2026-56817", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56817 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:905c49bc-1fe6-50f3-b987-e09ee757a382", "id": "CVE-2026-56818", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56818 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:d7146169-67bc-5e16-8829-052898a78d32", "id": "CVE-2026-56819", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56819 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:eaf2c368-8847-5819-98be-5dd5333dfa22", "id": "CVE-2026-56820", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56820 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:0fdbb010-d8fe-548d-9b38-7170934376f0", "id": "CVE-2026-56821", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56821 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:8d8c57e5-228f-5545-898c-7b7b41ef5ddf", "id": "CVE-2026-56822", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56822 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:e49013f4-3c9e-599d-b5e4-56157ba5f793", "id": "CVE-2026-59898", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59898 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:5ce02c94-ef39-5c0b-9e94-e75d5e7622b7", "id": "CVE-2026-59899", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59899 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:2e020eb6-3e72-5183-bcfa-7fb54784e067", "id": "CVE-2026-59900", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59900 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:3824d97b-e8ed-5825-9cbb-da78d1f4c7e3", "id": "CVE-2026-59901", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59901 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:cd4b59d7-b243-54b6-930f-0b134517063b", "id": "CVE-2026-59902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59902 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:40814a5c-cab1-5dd1-9c83-320520d39e5c", "id": "CVE-2026-59903", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59903 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:a24d6700-236c-55d5-85f4-d29e0d36f2ee", "id": "CVE-2026-59919", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59919 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:44bbdadc-8131-5643-b430-b0f8ba146baf", "id": "CVE-2026-59920", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59920 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:1854f98a-6d47-5bac-a9a1-5833c058035f", "id": "CVE-2026-59921", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59921 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:21db0730-a917-50dc-a8b6-2102becba33b", "id": "CVE-2026-73507", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-73507 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:db33d853-d356-574b-bcc1-e002861394f6", "id": "CVE-2026-73508", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-73508 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:5c27d031-2302-541e-a8f2-01bb7d8905ea", "id": "GHSA-mfg7-5gfp-c4w3", "analysis": { "state": "exploitable", "detail": "Vulnerability GHSA-mfg7-5gfp-c4w3 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:a027cc49-5960-5e1b-a3c7-6705dbff1105", "id": "GHSA-v74w-7mr3-4qg3", "analysis": { "state": "exploitable", "detail": "Vulnerability GHSA-v74w-7mr3-4qg3 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.1" } ] }