{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:4433592c-9e94-5761-9a84-99f8d5b0b608", "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.1", "type": "library", "group": "io.netty", "name": "netty-resolver-dns", "version": "4.1.122.Final-tuxcare.1", "purl": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:4f2f156a-7e75-5c82-8721-d7e239b26524", "id": "CVE-2025-55163", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-55163 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:6ce152de-1efa-57af-8b65-99a3ec6dd724", "id": "CVE-2025-58056", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-58056 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:1a83c155-d3a8-5a61-9e74-94ec90025313", "id": "CVE-2025-58057", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-58057 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:d1e92f73-c215-5a03-a27b-baad9e9e05b5", "id": "CVE-2025-59419", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-59419 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:78486e49-85b1-5fbc-b2c3-53e49b15fd9d", "id": "CVE-2025-67735", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-67735 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:6bab4dc5-45a6-5cbb-a586-a7ac3513c933", "id": "CVE-2026-33870", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33870 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:49347ed2-a69a-583c-8769-6338e8f07a95", "id": "CVE-2026-33871", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33871 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:7a3c0f58-99a7-584b-9b7a-ca71512e9840", "id": "CVE-2026-41417", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41417 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:b4a4cf21-f56c-5429-a490-1b1433c1ee94", "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-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.1" } ] }, { "bom-ref": "urn:uuid:76313fca-7a24-5045-bf27-9735cdb3f2eb", "id": "CVE-2026-42578", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42578 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:519fbc11-6cbc-5a5e-a6b1-8bc5b527c8e8", "id": "CVE-2026-42579", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42579 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:6c1680f7-e735-5533-9c92-edd80ebd2973", "id": "CVE-2026-42580", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42580 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:0466a730-d532-5a31-8232-4361b7c7f96c", "id": "CVE-2026-42581", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42581 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:990d323b-8c2a-5c9a-a715-cc3110fced6d", "id": "CVE-2026-42583", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42583 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:585326a4-7f96-5c01-b26e-3cd273fdb8f8", "id": "CVE-2026-42584", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42584 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:670931ff-cc4d-5eed-b044-596affd2cfe1", "id": "CVE-2026-42585", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42585 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:178d2d21-8539-5a33-9643-8baee37a4818", "id": "CVE-2026-42586", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42586 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:7c439fe0-37e5-5707-988f-95da89f473c5", "id": "CVE-2026-42587", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42587 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:7a27e9cd-96a0-518d-a218-56a35d342e42", "id": "CVE-2026-44248", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44248 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:c0c8efa4-e246-5c12-87ce-ecb218cfef2e", "id": "CVE-2026-44249", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44249 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:a104484c-6824-55a0-8ac0-61fb6fc7c1b7", "id": "CVE-2026-44250", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44250 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:1b548799-663b-5920-b000-3e59455ee510", "id": "CVE-2026-44890", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44890 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:78083c8c-06d9-5b01-a1af-c4452d53dacb", "id": "CVE-2026-44891", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44891 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:5ce74bdb-6562-596a-a4f4-567a2e78de40", "id": "CVE-2026-44893", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44893 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:05f3f387-f303-53e8-b776-dc8e99efdccb", "id": "CVE-2026-45416", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45416 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:2841e5ff-f6b0-51f3-ae71-79d06e7aacdb", "id": "CVE-2026-45536", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45536 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:89817c0c-10c8-59f9-b255-732065c4fc78", "id": "CVE-2026-45673", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45673 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:96d57395-5dc0-58e0-a4a9-96c741be5e3e", "id": "CVE-2026-45674", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45674 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:b2cacc86-cb8e-595e-95f8-0639174399dd", "id": "CVE-2026-46340", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-46340 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:8b7e06aa-0b79-59e4-9c94-23f3663173ae", "id": "CVE-2026-47244", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-47244 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:95c35fbd-fc82-50ee-bdcc-43a39604a25d", "id": "CVE-2026-47691", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-47691 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:8fa6afb1-eb03-57af-b4de-df02cd56ffb0", "id": "CVE-2026-48006", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-48006 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:a1197498-75b6-5407-a06e-624e32dc56bf", "id": "CVE-2026-48043", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-48043 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:4eb057fa-1dc2-53e4-9288-695ec2fe7679", "id": "CVE-2026-48059", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-48059 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:0966c545-e833-5a6b-8cce-20078694382a", "id": "CVE-2026-50010", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50010 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:65bf2b23-8bee-5677-a93f-26f244852a49", "id": "CVE-2026-50011", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50011 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:6b940610-de06-5222-9cff-335a72087567", "id": "CVE-2026-50020", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50020 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:0a8fc04f-f3e5-5d74-b8c2-5cb5024bd387", "id": "CVE-2026-50560", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-50560 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:f50de01e-1ba2-59e4-9f85-b8a4905db80b", "id": "CVE-2026-55831", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55831 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:4d8d9e00-d98c-53f9-a051-9371f471a476", "id": "CVE-2026-55833", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55833 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:939d2361-4fb6-5795-9319-63c80409b19c", "id": "CVE-2026-55851", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55851 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:14f1968a-7003-525d-bce8-9f48fce79fd8", "id": "CVE-2026-56745", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56745 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:771bd2cf-0496-5f3d-88fc-f829011e2a6c", "id": "CVE-2026-56746", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56746 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:f5253fe3-bab1-54e0-83ad-af091a7cf952", "id": "CVE-2026-56817", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56817 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:0740eebb-19cf-5944-8577-ba63ace3027c", "id": "CVE-2026-56818", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56818 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:d3b41ab2-4cfd-57e9-a4ff-4c7bd90df05b", "id": "CVE-2026-56819", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56819 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:55691d48-dbf5-5a2c-8c96-a859d05586f4", "id": "CVE-2026-56820", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56820 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:b986dcf6-2195-5806-a387-065d96679b72", "id": "CVE-2026-56821", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56821 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:3d32731c-ce99-59b8-9de8-7fe3e5dd3c03", "id": "CVE-2026-56822", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56822 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:4d59bbb0-1e0a-510b-a25a-d1dc4435089e", "id": "CVE-2026-59898", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59898 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:35cdcd21-68e6-5c98-a990-e7a29b1e0ee4", "id": "CVE-2026-59899", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59899 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:93b95b26-2b77-516b-9a1d-84f59fb622c7", "id": "CVE-2026-59900", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59900 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:03adaeb7-601f-56d8-a1eb-3e7bc947d671", "id": "CVE-2026-59901", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59901 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:d9fddcf1-bc36-5af2-be7a-73626db47fc8", "id": "CVE-2026-59902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59902 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:c74fc5b0-d95f-5822-82aa-2bac391e4728", "id": "CVE-2026-59903", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59903 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:e1552b01-7d88-527f-8ee6-2777d42e48e2", "id": "CVE-2026-59919", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59919 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:88cf1acf-3f76-5ef6-b4f0-b4ca3d0d9eb9", "id": "CVE-2026-59920", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59920 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:eff35370-1bbb-5ff1-8656-814c874d6e76", "id": "CVE-2026-59921", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59921 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:ee55619b-77db-5d47-97a6-f215319a3fde", "id": "CVE-2026-73507", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-73507 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:cdf151ed-d10d-571b-b9f3-d2428fbaf71f", "id": "CVE-2026-73508", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-73508 affects version 4.1.122.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:183451e6-4eb1-544b-9dc4-f2a77e28117b", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:79d71d8c-a372-5fd8-93cb-42228bdcbd06", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.122.Final-tuxcare.1" } ] }