{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:0616bd2f-083b-58fc-bfc5-5576f169a387", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3", "type": "library", "group": "io.netty", "name": "netty-codec-dns", "version": "4.1.130.Final-tuxcare.3", "purl": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:566e2b2c-ff66-5ef7-bd93-0ff6db6ccb16", "id": "CVE-2025-55163", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2025-55163 does not affect version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-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-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:fe2c5e77-d40c-5b27-a0d9-b6b80ece37c1", "id": "CVE-2026-33870", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33870 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:70a3bd12-d601-55bd-a9ec-e3e281a94c5e", "id": "CVE-2026-33871", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33871 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:9b1ca547-9486-5613-bde2-a90da2c5d027", "id": "CVE-2026-41417", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41417 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:4339163f-8223-5ffe-844e-cf579f73304e", "id": "CVE-2026-42578", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42578 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:4654bcc3-0226-539e-8b81-10be702fef2e", "id": "CVE-2026-42579", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42579 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:6f046550-15a1-54af-b2d5-f93d9fe2134e", "id": "CVE-2026-42580", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42580 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:71264b4d-13be-5786-a56a-62224eccf8ca", "id": "CVE-2026-42581", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42581 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:c6f2b916-97db-5441-9d96-3831a5ec94f2", "id": "CVE-2026-42583", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42583 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:a12e563e-de35-503f-88b1-05f42c9ff847", "id": "CVE-2026-42584", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42584 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1a485c80-d423-59a2-9fe1-7f2cd648af47", "id": "CVE-2026-42585", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42585 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:bf57c442-6165-5f01-a147-7e247b932e11", "id": "CVE-2026-42586", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42586 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:8d9f98ca-5023-512f-b84a-21c859619f8f", "id": "CVE-2026-42587", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42587 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:27a1b4a1-3e23-5c19-8a6d-905cc587e905", "id": "CVE-2026-44248", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44248 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:44c7245d-2edb-5705-ab6b-8d19cc89cc68", "id": "CVE-2026-44249", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44249 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:5c94ac38-aa7f-51e8-b5c4-2bfe57071b88", "id": "CVE-2026-44250", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44250 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:67ca2c4e-c81f-5d13-be1b-cb151109aa6e", "id": "CVE-2026-44890", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44890 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:875018c8-1c40-5371-ad15-31ca47eb93f3", "id": "CVE-2026-44891", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44891 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:dbc5f6a2-3400-5b63-a754-9e737c3ae0eb", "id": "CVE-2026-44893", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44893 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f79ad88f-bb1d-520e-81e1-6034ceacad79", "id": "CVE-2026-45416", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45416 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:76fffe5f-bd7e-57e3-93e4-eaad289a78b2", "id": "CVE-2026-45536", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45536 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:42a3dd49-f2c9-5d99-9e88-19b41afd7a90", "id": "CVE-2026-45673", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-45673 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:8ca94373-89c7-53d7-94cb-530ed6099225", "id": "CVE-2026-45674", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-45674 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e1b2492f-0a6a-5625-906b-7983602b3316", "id": "CVE-2026-46340", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46340 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:46a63dec-3282-5757-8d86-a5f5e44a9ee1", "id": "CVE-2026-47244", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47244 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:262eeae6-9994-5cbd-b570-e9b35afb6a9a", "id": "CVE-2026-47691", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47691 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:25c13a76-5c1d-55f9-853d-fdb093e02215", "id": "CVE-2026-48006", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48006 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:22f67b4a-b4ef-5c5d-b980-1aec333a818f", "id": "CVE-2026-48043", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48043 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:2db05233-a3df-5254-9c03-dc87e2b44ae1", "id": "CVE-2026-48059", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48059 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e54ab55e-1e7e-5209-933a-be92b87d274d", "id": "CVE-2026-50010", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50010 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:6243d1c9-840a-5528-a498-462bf3334821", "id": "CVE-2026-50011", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50011 does not affect version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-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-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:9d9902eb-0ee4-543b-85b8-a8842b1148a9", "id": "CVE-2026-50020", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50020 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:22a84b2d-b1b7-5544-854f-c6067b5d251f", "id": "CVE-2026-50560", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50560 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:6e268fec-0e4f-578c-8bce-b94fbe75fdc8", "id": "CVE-2026-55831", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-55831 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:ceca9f86-57ad-5242-99e9-7c3722754087", "id": "CVE-2026-55833", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-55833 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:a74a9771-ee16-5c4f-8cb8-20c0012fd5b5", "id": "CVE-2026-55851", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-55851 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:93b522f8-08c2-53f9-b198-d2febc44fc07", "id": "CVE-2026-56745", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56745 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:9156cf54-6e03-5598-9020-5f66e3340896", "id": "CVE-2026-56746", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56746 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:3b76f729-0112-5dff-8ac0-0dac1d1690d5", "id": "CVE-2026-56817", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56817 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:01621aeb-fefd-5478-a024-ea5aea4308f2", "id": "CVE-2026-56818", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56818 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:01a6cf1e-dd73-59be-952a-55b787a862bb", "id": "CVE-2026-56819", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56819 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:051211bb-8aed-56ea-98a6-1aee8edb15cc", "id": "CVE-2026-56820", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56820 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:3ebba10f-256f-568f-bc49-a71b7e939201", "id": "CVE-2026-56821", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56821 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:6e80d0f0-f5f0-5ff4-889e-3aa28dbc8e02", "id": "CVE-2026-56822", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-56822 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f5a66d98-2500-597b-a440-45a083025ff7", "id": "CVE-2026-59898", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59898 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:bb728807-da52-520d-ac68-01ce032b6b22", "id": "CVE-2026-59899", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59899 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:b550f2fc-c8f7-5da1-8da1-13d05894dd30", "id": "CVE-2026-59900", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59900 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e407e334-75b3-5f42-aa08-78976c3508bd", "id": "CVE-2026-59901", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59901 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:07b167c9-528c-5cb7-925f-71be9da23bec", "id": "CVE-2026-59902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59902 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:3d744988-b25d-587b-8e9a-73f38c72d7f7", "id": "CVE-2026-59903", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59903 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:766bb6d1-c323-5e13-a47e-48981c515c2d", "id": "CVE-2026-59919", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59919 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:cc024bde-fc70-5e1e-848e-8e949905fd1b", "id": "CVE-2026-59920", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59920 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d7f64a23-276b-56fa-b17b-76c122125ff8", "id": "CVE-2026-59921", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-59921 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:2583d23b-8b66-5967-a9eb-dffbf2bf3c6e", "id": "CVE-2026-73507", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-73507 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:bfeacaeb-4a23-50c2-aad7-a7e462d9801e", "id": "CVE-2026-73508", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-73508 is fixed in version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:362b016c-5ced-5a03-8df6-d3fdc9ef7bc0", "id": "GHSA-mfg7-5gfp-c4w3", "analysis": { "state": "exploitable", "detail": "Vulnerability GHSA-mfg7-5gfp-c4w3 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1ac4f1d9-5ec1-54b4-b78a-b571ba1e2419", "id": "GHSA-v74w-7mr3-4qg3", "analysis": { "state": "exploitable", "detail": "Vulnerability GHSA-v74w-7mr3-4qg3 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.3" } ] }