{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:7892d467-40ae-550c-b75e-cdd9d30492cf", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4", "type": "library", "group": "io.netty", "name": "netty-resolver-dns", "version": "4.1.130.Final-tuxcare.4", "purl": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:5d722056-f980-5172-ade1-bee71d84a5cb", "id": "CVE-2025-55163", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2025-55163 does not affect version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns. already_fixed \u2014 The target Netty 4.1.130.Final repository already contains the complete MadeYouReset (CVE-2025-55163) mitigation. The Http2MaxRstFrameLimitEncoder defense class is present, integrated into the HTTP/2 connection handler builder, and enabled by default for servers with a threshold of 200 RST_STREAM frames per 30-second window. All protocol-error-triggered RST writes route through the protected en..." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b3607d98-aa86-5896-8eab-ce90768bf475", "id": "CVE-2026-33870", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33870 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5b95bcd2-0a34-5237-846d-ff4943e658fb", "id": "CVE-2026-33871", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33871 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b6efaab9-a778-57ef-854e-de0af721bb2b", "id": "CVE-2026-41417", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-41417 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1452d9bd-9815-5377-8f27-8c574bdfa729", "id": "CVE-2026-42578", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42578 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1a853920-a3a3-57d7-9014-bb22ef4fef3d", "id": "CVE-2026-42579", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42579 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6cd94a15-266c-562d-9892-1798e25dddcb", "id": "CVE-2026-42580", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42580 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e8293dda-8e67-5cc1-8c27-e2353168310d", "id": "CVE-2026-42581", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42581 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7b2cd4fd-d354-5cdf-b376-a7ac06ba43d6", "id": "CVE-2026-42583", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42583 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:854602a4-1de6-5fb2-b2fd-a64853caa4ad", "id": "CVE-2026-42584", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42584 affects version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:32ed2877-47f5-55c5-85fb-ebd5abad2835", "id": "CVE-2026-42585", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42585 affects version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:37ff291a-d01e-5c9a-b919-00bc602a4790", "id": "CVE-2026-42586", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42586 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e93c3675-2fa4-5a74-853a-ba8e0639cf86", "id": "CVE-2026-42587", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42587 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:065334c3-7deb-56cb-9d45-3556860ec954", "id": "CVE-2026-44248", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44248 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c16d2f13-23e4-5eba-bd1c-36efa33731c5", "id": "CVE-2026-44249", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44249 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:07f8fd62-7912-5c9d-a9ff-ff52a8c7cb3d", "id": "CVE-2026-44250", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44250 affects version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:dea980e7-cdce-5f49-ac9a-88da76011619", "id": "CVE-2026-44890", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44890 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7bfb49b7-fdda-5791-8521-4196d703e063", "id": "CVE-2026-44891", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44891 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:fbaa6ce4-94dd-55a9-a9bf-8decff4eb3cd", "id": "CVE-2026-44893", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44893 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3ff0a932-c205-55b8-b3d1-d901d92b3f0e", "id": "CVE-2026-45416", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-45416 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f0982247-cbda-5f6f-9ee0-4109ddd01deb", "id": "CVE-2026-45536", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-45536 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d60e6107-0c85-5721-bf14-0282dad35fed", "id": "CVE-2026-45673", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-45673 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:30f1f9f5-16d2-58f0-b26c-b14aa6d788d3", "id": "CVE-2026-45674", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-45674 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5835de18-f469-569d-af7a-53b172a92c5a", "id": "CVE-2026-46340", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46340 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:33c7ac0e-2d0d-5cb3-bf5c-6d84ed1ec7e0", "id": "CVE-2026-47244", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47244 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7afbafab-1c31-5dc7-aef8-e5157886338d", "id": "CVE-2026-47691", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47691 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d74c8a1f-b891-5b95-bbfa-2b810424809f", "id": "CVE-2026-48006", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48006 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6025b224-88fc-5688-98eb-43e80d5f07de", "id": "CVE-2026-48043", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48043 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6e9c6ff3-b290-5251-894d-54538a293134", "id": "CVE-2026-48059", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48059 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:2341b640-a363-5118-b3e6-ce1493aee217", "id": "CVE-2026-50010", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50010 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a8c95397-2db5-50ec-a083-facc6b909fe2", "id": "CVE-2026-50011", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50011 does not affect version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns. Patches already applied: bff98ee51b5d0b7ee25fd5005f2169f2a0467efa (already in target via d5b4e38845f5 'Backport CVE-2026-44890 to 4.1.130.Final')" }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8a2d5c83-f591-5def-8625-4168f6497639", "id": "CVE-2026-50020", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50020 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d285a834-3dc0-5f3a-b97f-2462f7972003", "id": "CVE-2026-50560", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50560 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c46d7fd4-190c-5a21-9088-41be79077e85", "id": "CVE-2026-55831", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-55831 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b154ed6d-d478-52a1-8edc-ac13f55a2bc1", "id": "CVE-2026-55833", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-55833 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:0aac7521-d1b2-554e-a535-702da91c9ebe", "id": "CVE-2026-55851", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-55851 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a2b347ef-2a08-5c55-83ad-6cc861220fd7", "id": "CVE-2026-56745", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56745 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:bb535aaf-ada9-5f75-b994-107ecef0d945", "id": "CVE-2026-56746", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56746 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7a096273-5d10-5206-ba22-9cebb1e6444c", "id": "CVE-2026-56817", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56817 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:26c8789b-f274-59c7-9679-84171645faab", "id": "CVE-2026-56818", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56818 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:97a2a8c0-b153-532c-a4cf-5eeaf949dfab", "id": "CVE-2026-56819", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56819 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ea1698d2-5978-5d6c-b847-8bd649a2acec", "id": "CVE-2026-56820", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56820 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:67aac265-8090-5a31-b5df-ecb603f354af", "id": "CVE-2026-56821", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56821 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:11da4e76-39da-5ac8-a376-ce2cc67d7abe", "id": "CVE-2026-56822", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56822 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a4c85e93-6a27-55aa-9ebd-2d4fd52d45f7", "id": "CVE-2026-59898", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59898 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d7fa15f4-5613-5202-b0ff-a680bdfb4a4e", "id": "CVE-2026-59899", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59899 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ae828197-dcd1-53a1-8685-cb155c61a233", "id": "CVE-2026-59900", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59900 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:54fe9b12-6175-5878-9179-23f1052cddb0", "id": "CVE-2026-59901", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59901 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1c02ab8e-5ec4-5724-9e2d-4188e95b4527", "id": "CVE-2026-59902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59902 affects version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:be8ff741-fdc3-5981-a08f-1e60713babbe", "id": "CVE-2026-59903", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59903 affects version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a2766488-3d6f-5089-988f-370cad26dbf2", "id": "CVE-2026-59919", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59919 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1df1bd55-9be6-52af-80a5-bb9af17312b6", "id": "CVE-2026-59920", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59920 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:49de28ee-8c93-53b4-ae57-493678f5cc63", "id": "CVE-2026-59921", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59921 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:462aeeb4-d869-50b4-b7cb-4b7e1154cdd6", "id": "CVE-2026-73507", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-73507 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8dda8ff3-0c37-564c-a00b-a87735e88993", "id": "CVE-2026-73508", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-73508 is fixed in version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:abc80e12-faf7-5630-a99f-0ef03be5eaab", "id": "GHSA-mfg7-5gfp-c4w3", "analysis": { "state": "exploitable", "detail": "Vulnerability GHSA-mfg7-5gfp-c4w3 affects version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:9a00aa60-e0d0-5f20-8b51-d696f6d78f57", "id": "GHSA-v74w-7mr3-4qg3", "analysis": { "state": "exploitable", "detail": "Vulnerability GHSA-v74w-7mr3-4qg3 affects version 4.1.130.Final-tuxcare.4 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.4" } ] }