{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:edef945a-7a4e-5143-91ab-cfc82e1cd991", "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.3", "type": "library", "group": "io.netty", "name": "netty-resolver-dns", "version": "4.1.130.Final-tuxcare.3", "purl": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:10e376fb-5017-57a6-a29c-da5db86d13f3", "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-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.3" } ] }, { "bom-ref": "urn:uuid:5cc2afe4-ef95-5fb5-9e6c-0ff883c43851", "id": "CVE-2026-33870", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33870 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:b6ff1400-c4fc-5128-889b-87855d958953", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:9c65deab-264e-5220-b028-a383e64557f4", "id": "CVE-2026-41417", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41417 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:171f3c39-0401-55e5-8ab0-16890e16b72a", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:24dfeffe-3d8d-5360-90f1-1c94ccacb624", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:79df659c-c0b2-558b-9f22-004423c06c38", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:10dcec8b-f895-5561-9cc5-bb43b5d99c05", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:ff6156a2-0061-56fe-a963-729b81a25283", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:0c7d6108-f302-5c3d-8125-ddce858044cc", "id": "CVE-2026-42584", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42584 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:2f1852d9-c62c-5b07-993b-e6d8a7d2ecde", "id": "CVE-2026-42585", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42585 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:03de917a-2549-5082-a074-6e48f647a2b5", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:aae00576-b888-5385-b855-e12e098282ee", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:802235e9-da35-5563-8b38-6f26583e678c", "id": "CVE-2026-44248", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44248 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:a5d92e33-6d8e-5853-90c8-371837dad715", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:87a91675-1d36-5c22-ae9a-01d570667873", "id": "CVE-2026-44250", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44250 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:bcd6411c-5283-5572-b355-d9fdf7053145", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:cc7b9500-906a-5c51-8cb5-4200ff46b778", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:edbfd527-83ca-5c28-908c-bf5fb27e40cd", "id": "CVE-2026-44893", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44893 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:b6e61f51-c812-5b4a-bd51-5bf608ce6e0f", "id": "CVE-2026-45416", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45416 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:857b45ed-6a3c-5d51-ac9c-459b933099a1", "id": "CVE-2026-45536", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45536 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:baa95418-be2a-5df2-bb50-16ae7a405079", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:2db55219-6921-5a7f-a1e1-2bb8b847a645", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:ebe4ce69-53cf-5d65-8cff-0156ae4ba103", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f837afd8-791a-5646-ba4e-2db91570f7e2", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:ead636d8-d217-5518-b34a-cea8d0d42e5a", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:978d60f2-ab1a-5a4c-b7ba-4667096fdcfb", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:12cb57f9-2fb0-535c-a6ba-e3f4f927836b", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f7cb9153-7293-566d-aa64-e1ecf43be5f3", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:3bdabfb2-83ab-5df2-8265-0260f28ae461", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:c68de75a-c445-5589-abf0-e6ceac751089", "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-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.3" } ] }, { "bom-ref": "urn:uuid:7a5a0b62-8b60-5b3d-8ca3-186de8c54a4a", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:7e7dc885-3230-5700-837d-5898d355a80c", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:5ec8ee50-ddac-535a-8d6a-4704c8589fd2", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:cfccb262-f3d3-5233-8fbc-99608338d7f6", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:3b242926-fd3f-5911-ab1c-02c450760ea9", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:238b78eb-abbf-5dd8-be44-de261d19281c", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e6abb37f-6f74-53fb-a501-f2224925705b", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e00aa0a2-b7d0-58e2-8219-4aa02288d647", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:a65c8e88-f6f8-519b-ae23-0259bf5f4c80", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:835055bc-551b-5b1c-bb89-b8bbcad46430", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:035823d6-41ea-5109-b6e7-4f4c176fd5c1", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f6f090f6-d5ab-5515-a97a-972806faf535", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:9f1a100a-535e-5eaa-b9b7-ca265c762ca2", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:7c3bcf0c-0009-5336-8be7-5e30604471dd", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:670acb2f-069d-5c82-9e36-826f02d6f2ad", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:69f892bd-aa65-5db6-b203-3d13a8a98eb8", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:0c01a3eb-eac7-5550-8bfa-e62ebddac7ee", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:26eff60b-08a2-5892-aec6-819025db9f89", "id": "CVE-2026-59902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59902 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1a3aff47-273a-5765-8b9b-12057dd4e0a6", "id": "CVE-2026-59903", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59903 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:0c2db930-1b8b-5311-9a59-c43d15cc8b03", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1eb468ee-5e0d-58c6-9985-2481e3e5e9bf", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:6101d93b-8740-5110-ba15-7518e4a79afe", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:7226ece5-8eba-57d4-8a50-0a8aeef1da45", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:0d45d666-dff3-5dd1-9ff7-be474b02e356", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:df76f5ce-0cbe-5761-9eaa-15fca75def3b", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d7c0beed-1e55-5372-9c01-0265db54466d", "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-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.3" } ] }