{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:2d39fea8-2c40-54ae-bbe0-6f8c64ce94a7", "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.2", "type": "library", "group": "io.netty", "name": "netty-codec-dns", "version": "4.1.122.Final-tuxcare.2", "purl": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:016bc697-a83b-567e-891c-88c59c65b618", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:dd453703-e2cb-5c41-8717-8a982a523642", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:9258e8c9-737f-531f-a350-c1b0ed74916d", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:67e335fa-fe24-5f04-b1b0-bae67e790f5b", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d4464d4c-8b0e-578e-9690-fefcd4b929c1", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:23236d18-bfd2-58ad-ba4d-49fe16f55cd6", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:34a8cbff-5321-5174-b669-cc2640e75863", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:5075a140-42be-51e8-b049-041ae9c366fe", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f09cf7ad-3caf-51ce-93b2-7f2d847752b4", "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-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.2" } ] }, { "bom-ref": "urn:uuid:1c05c97b-d9d1-54a0-afa0-d01432540738", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:813f400b-81ae-5164-b10f-69c15343bf91", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:83b9d938-e1cc-5f5c-9e62-0699222d483e", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c6ca2317-bb1e-57b0-b9a9-eb0242952770", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:06436ea4-b60e-5ad7-b067-be39928d106d", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f9882f1e-be4d-5ba7-99a3-0021a87e4082", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:fee07739-6e22-5ae5-9eb0-1105f1f98990", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:16f5ed77-eae9-541e-8ea7-5ff3b4795c48", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:2ce1b661-e6f4-5b84-ba9f-bb8f89f5c528", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:b609d6f7-2071-540d-b788-048f073d38b5", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:fdfae1e5-0c24-59b2-a5fd-88935fec48a6", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e4d042f3-4945-57fa-8b02-6b03d21b2722", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:6e4181b0-3371-5127-af39-ea447e1ef976", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:1a39f736-472b-5520-9362-9a79da5cc82b", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:7fbb3744-bd0b-58f1-9b6a-8e9054e15c4b", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:b4fbbbab-6882-5d54-a08e-1a5e74426336", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d5b7b470-8f18-524a-801d-48123dbc3aac", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d95cf98a-fc60-58ec-8352-6805b914aa60", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:54021e97-3535-5f12-bba2-875307505dfd", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e8356c03-eebe-5be3-8f0b-1f0b781ffa33", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d5a5056f-715d-5ae9-80ff-b6d785ebb977", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:87932f2b-e809-5b13-b074-a47f06d6a15d", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c9467d25-6e95-5119-a9b7-c1048403eb61", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:7cd55558-c1d0-5387-9e20-229865d06123", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:966d2f21-c461-51dd-aaee-e2c21a05704c", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:65b22187-4f60-5936-895b-cca36a8dc8cd", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:770de7a2-3a11-5078-bdfe-347f74747f71", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:767ce1c8-4044-5279-8c0b-8a0363cc829f", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:5bd9c1b8-0cc4-556c-85bc-83e37eaf2943", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:30687ed9-6adb-5a3e-b19d-736561162e90", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:8b4231fa-9ef7-5e5a-9530-d071104ccc7f", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:9c9b3a33-0a5b-5a2c-a203-21d0aa7ab64c", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:53c3ab36-7713-574e-a1cb-9fd322e984b6", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:7924e494-0349-57d0-9fab-a2d54c9c0d55", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:dfa87b76-509b-505c-8fca-fc637c7988af", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:9ed026ba-e982-5478-a977-d3af873500b2", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:07c91857-d83f-5850-8643-5361d126b8c6", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:63308a7a-648b-5b16-89a3-b036a9077841", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e14850eb-6a5a-5472-be4e-80a7437c0d71", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:da7166e0-35eb-533f-8a08-edc51b1b0103", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f22b9d34-a90a-504b-8f00-f960c4b5e33f", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:39338919-b023-5d3f-8e06-7397a3a1728b", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:cb890fc3-f282-5f59-b014-2e54657193c6", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:948251e0-e282-5002-abbd-517d77e9eae2", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:21e6e5f4-f123-50bf-93f4-4ea215e92a6d", "id": "CVE-2026-59902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59902 affects version 4.1.122.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e75f0f2b-78ed-5656-9a0c-d25d9774b3a2", "id": "CVE-2026-59903", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59903 affects version 4.1.122.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c6603387-a31d-5bda-bbd8-6c57f0b6196a", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:2f0c9ece-80e4-54d9-8c86-f3b7ba0b012f", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:6536b734-d57f-5633-9cec-5092d5bb05b2", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:3767ac73-5577-50f5-a1c1-8dcef2beffe9", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:7e321519-3591-542d-8560-024387c0cc7a", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:55078fcf-f5d2-5e3e-8044-e396f7fe8d9f", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:1c435797-f037-56d3-9081-db7b06c64281", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.122.Final-tuxcare.2" } ] }