{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:fa62294a-386d-590c-a0c5-4544623862f0", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2", "type": "library", "group": "io.netty", "name": "netty-resolver", "version": "4.1.122.Final-tuxcare.2", "purl": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:d6343ac9-5a71-5854-a3a8-d9bf6e7e2ea1", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:cc7186a0-2e8f-5788-a878-73e3e473f869", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:7abe563a-531c-56d6-8fc0-53e2fe0a322d", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:1772eb73-4e32-52a8-93e8-61a9f8555045", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f0ebd97f-fbf6-5a61-83b0-2d137f7feaf1", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:814bb9e5-4fe3-5669-a294-76525096526a", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:38c34cde-ca1a-5fc6-aa65-6d607207a815", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:ce1b3c73-2a81-5db3-88ae-d0c612ed306d", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:0a275f83-a701-5a2c-9ee0-c280aae7cd70", "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. 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@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:b52ea15f-6d39-55a5-8e3e-67814ed84160", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:68b02875-dc77-5eb7-b1c2-66166dde23bf", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:11ac5db0-ed00-5aeb-9da2-a5f7033fdcbb", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:377b967c-405a-5941-a9f3-59e4b77ffb5c", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:039ca8ac-e545-56ff-bd5b-c2fde197cbc4", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e3eec793-dba0-50ac-9a30-0696652ea458", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:620385b4-c175-5cec-8b6d-692f10840b47", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:ab15a13b-c3ea-575d-b102-8887bad5f1cd", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:98967e08-85d4-52e3-b69c-6c1890146052", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:a7d2ef8d-f3ec-5e20-a900-2f578fc54781", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e2793984-7ecd-5e75-ab6d-09c8e5e80074", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:51ae5271-dd0c-515d-9bc4-51d0bf1b50fa", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:338b1564-2bb1-541f-b7e9-325d7187bdf7", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:bb78b3dd-248d-5e42-87a3-d7398f512c31", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:76bf82e1-b83f-5397-9bbd-7680667b490c", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c557b8bc-8fcf-534a-b216-fc6afd4471e5", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:09ea49ab-940c-54a5-af3a-b8f6bd7b5fe6", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:5ae0813b-17f0-581f-a546-bcd761925a5f", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d79049e5-7bce-5d7e-9a05-b9e4f286f824", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:679de742-7df4-5770-b4ad-9390ab61d471", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:29e6b6e9-645f-51f4-817e-2305e72cca93", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:6abc62bb-e98f-5203-b523-503bdc4c012c", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:aee850b8-1503-56de-be40-f119cb59f6f9", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:01907e2f-a981-5d7d-b2c9-b4ba81c6141f", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e4bd5c7f-b44f-5627-8d1c-bef191fe416d", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:78c4460f-97d3-5287-9def-a3bf8ba38d66", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:7724fa27-08b8-597a-951d-f68a5fc74980", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:2c807857-58aa-5dd8-b6d2-4c3b78915493", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:0c8719f8-698a-59b2-af83-b6bf103aedc5", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:79c46b9a-cfa8-56ae-a442-0f68af523b30", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d9a9850a-5b61-5ed7-b1fa-c9d229459216", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:cdd97135-cdef-56f8-baa9-46dd0a2c870b", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f88d2cfd-e12f-5de3-ae2b-df4a001ea426", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:fc60a763-5e6b-522b-ad56-ef228fc8bdd6", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:0d39127b-6fd0-5940-8d6c-65f1f6075d69", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:aaab86a4-2722-5e0c-b8ff-a58a6487fb50", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:46a82c3e-36ca-5481-a62d-51e80bdc51e4", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:7b3f5a43-e51b-5fe4-b592-ca39f3f5c3c2", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:5c54a49e-b706-56b7-a2ff-e780e21e5bbc", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:76b641c7-9177-5e87-859d-0d9f2d80d156", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:20aafdf8-4f62-50c2-a10c-8f17cee3a84b", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c35144f2-1b03-5177-aa32-dbf81d76c445", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4b1177a7-bb05-5d61-bafd-82cbc3a0dca7", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c4d33686-5eb7-5519-99db-2863511d8ab5", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f667edd4-3325-5282-8059-0ff7814be69b", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:18ab71a0-9f3c-5ee3-be85-be09a89dd41e", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:01379fa5-d3b7-5e6c-9c8b-cd81e3e165b3", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:05361bf0-1adf-5145-ac1b-27a922fb3f49", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:ee53c226-a23b-5753-a7fd-6888b74fbcdb", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c092f40b-473d-554a-8197-3de69acae430", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:93c5e8dc-b497-542a-8cd7-4363f8e88d99", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:55ac8fb4-06cd-5b71-8067-f0bd0021c784", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:5983966d-c43a-509b-b3bd-f15786ae907c", "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." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-resolver@4.1.122.Final-tuxcare.2" } ] }