{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:6553790f-5ef4-5f98-92b4-e670aaa022a0", "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.2", "type": "library", "group": "io.netty", "name": "netty-resolver-dns", "version": "4.1.130.Final-tuxcare.2", "purl": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:14ef35f6-84e0-59b9-a56e-1e48e66b0371", "id": "CVE-2025-55163", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2025-55163 does not affect version 4.1.130.Final-tuxcare.2 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.2" } ] }, { "bom-ref": "urn:uuid:708b10a7-7636-50db-ac14-8f54dd24fc45", "id": "CVE-2026-33870", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33870 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:0d517250-7e65-51ac-bee7-b0fc7d7886df", "id": "CVE-2026-33871", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33871 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:5ba13d7d-d153-5c48-91fa-5c16546e344e", "id": "CVE-2026-41417", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41417 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:11111e75-ad44-55cd-871b-49117c17d6fd", "id": "CVE-2026-42578", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42578 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:119c9de8-b239-584e-b2f3-1a7ccbe93f0c", "id": "CVE-2026-42579", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42579 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:daaca8d3-4551-5811-a132-7f5919d10008", "id": "CVE-2026-42580", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42580 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:af4d0468-9578-528b-b925-c886290ed4ec", "id": "CVE-2026-42581", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42581 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:605711a6-8683-5eee-af88-1fabc9e0ec60", "id": "CVE-2026-42583", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42583 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c9cfe1af-a22e-5d29-a3c0-0f07415366b8", "id": "CVE-2026-42584", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42584 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:2ffdbba4-2395-5281-8bc8-65d824360c20", "id": "CVE-2026-42585", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42585 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:fc338290-85c9-516c-9975-fd7a295ebf25", "id": "CVE-2026-42586", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42586 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:9e7d46aa-f9ad-5287-9f6e-c47a79371b3a", "id": "CVE-2026-42587", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42587 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:8600e7af-1d86-5881-8e6a-ded93fe57ed9", "id": "CVE-2026-44248", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44248 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:0f84958b-ea6d-5b7e-9342-d104e67c244f", "id": "CVE-2026-44249", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44249 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:40478e13-e7ca-5c45-843e-6411b0488a85", "id": "CVE-2026-44250", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44250 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:7c53a288-2f6d-59a2-9e4f-317b8aaf7420", "id": "CVE-2026-44890", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44890 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:2472df9b-f784-5ef1-8fc4-58e559631d9a", "id": "CVE-2026-44891", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44891 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:01a548a4-7afd-54f7-a398-9afbe3e375b7", "id": "CVE-2026-44893", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44893 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:125227fa-dbf1-5a28-afd1-33e1904930ce", "id": "CVE-2026-45416", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45416 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:22aa9e72-4ee4-501f-959a-76907223f38c", "id": "CVE-2026-45536", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45536 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:1aa5bada-2939-59bc-8d01-2159b4faff54", "id": "CVE-2026-45673", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-45673 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:b5a66fb4-2744-59db-a452-888e502c37ae", "id": "CVE-2026-45674", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-45674 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:09a94d63-b1e4-5821-bb02-7d3e216f6ae0", "id": "CVE-2026-46340", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-46340 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:85b1d651-05b7-59a1-bc20-aab03119a756", "id": "CVE-2026-47244", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47244 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:6c03998d-1c98-520c-9fc9-7e35a89ca0f0", "id": "CVE-2026-47691", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-47691 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:2cf96ecc-5222-5e89-b329-e2e6a4f0191f", "id": "CVE-2026-48006", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48006 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d84c3754-31d2-50cb-8122-5cf255fabce1", "id": "CVE-2026-48043", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48043 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:fc3798bb-4b6f-572d-aceb-05bf4723c2d0", "id": "CVE-2026-48059", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48059 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:630f1a9e-2dab-5745-b5c8-db5dc0a6420b", "id": "CVE-2026-50010", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50010 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:46cd23e5-2d2d-5642-8f4a-55cb08276a30", "id": "CVE-2026-50011", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50011 does not affect version 4.1.130.Final-tuxcare.2 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.2" } ] }, { "bom-ref": "urn:uuid:1535b85c-3003-52c7-8753-bd7e846d9c13", "id": "CVE-2026-50020", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50020 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:590c864c-2346-54b4-a495-bcfdeed1c003", "id": "CVE-2026-50560", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50560 is fixed in version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:b54afe6c-98e6-54df-96f5-a078f7b89673", "id": "CVE-2026-55831", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55831 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e1fa1400-6301-5eab-bef6-5d51b2312669", "id": "CVE-2026-55833", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55833 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:0a5c150c-1fae-58d8-b42f-4ae19bb1eb3a", "id": "CVE-2026-55851", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55851 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d4f6b0cf-43b0-522a-b758-850f91bf006e", "id": "CVE-2026-56745", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56745 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:8a1d665a-7384-5c04-a2c9-8616a840b290", "id": "CVE-2026-56746", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56746 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:9c9e90b0-be1d-5e9b-8af2-ac771b225ae8", "id": "CVE-2026-56817", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56817 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:cee20e4b-6793-5c8c-becb-898d0401790d", "id": "CVE-2026-56818", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56818 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4c458071-9fdd-5501-b433-171d509ce693", "id": "CVE-2026-56819", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56819 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:290c9e17-129b-503a-bb8e-fc83ecb1c4b0", "id": "CVE-2026-56820", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56820 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:34cc2ad0-ad5c-54c1-94c6-226aa7af5b27", "id": "CVE-2026-56821", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56821 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e7210c90-e890-5d1f-b7ca-785fafa2897d", "id": "CVE-2026-56822", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56822 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:612ad503-9d96-5d5f-b898-224c9211ba6f", "id": "CVE-2026-59898", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59898 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:a17df138-85be-5f95-8b33-c370b4bdfb63", "id": "CVE-2026-59899", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59899 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:91e9a04d-3f5b-516a-b2a1-79b81064814f", "id": "CVE-2026-59900", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59900 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:53e87994-20c0-51fd-ab50-f066d2084238", "id": "CVE-2026-59901", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59901 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:517ac538-4797-50a9-a391-fff752ec1729", "id": "CVE-2026-59902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59902 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:1f640107-3bb3-5d64-92d3-150fdd8abc3b", "id": "CVE-2026-59903", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59903 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:333e3b95-68d8-569d-a131-0aa26493317e", "id": "CVE-2026-59919", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59919 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:9428e230-a6f1-542e-8b39-55635c3328a7", "id": "CVE-2026-59920", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59920 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:72b84ae5-8e59-5d5c-89d3-c96e62f1b4c9", "id": "CVE-2026-59921", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59921 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:6dee4b3a-133e-5cb3-abc3-f8f2617d2283", "id": "CVE-2026-73507", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-73507 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4f407152-e6b0-5e01-881c-0a3c20714c79", "id": "CVE-2026-73508", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-73508 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:60ee4f00-2ec8-5cd0-8fdc-cc0c71805ab1", "id": "GHSA-mfg7-5gfp-c4w3", "analysis": { "state": "exploitable", "detail": "Vulnerability GHSA-mfg7-5gfp-c4w3 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:74b7d3c1-3721-5b5c-85e3-6ca0aa11789d", "id": "GHSA-v74w-7mr3-4qg3", "analysis": { "state": "exploitable", "detail": "Vulnerability GHSA-v74w-7mr3-4qg3 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.2" } ] }