{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:1db305f8-e938-5187-9ca1-098675c05933", "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.2", "type": "library", "group": "io.netty", "name": "netty-codec-dns", "version": "4.1.130.Final-tuxcare.2", "purl": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:aaeae427-22e7-503c-8c1b-a04f3cc32a71", "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-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.2" } ] }, { "bom-ref": "urn:uuid:427080b3-b3c4-51a7-a062-7f1cc12ab5a0", "id": "CVE-2026-33870", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33870 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:9f1d5543-650f-570d-b0be-183dc892155a", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:2846c52c-9a83-51a7-9d17-9c1752980364", "id": "CVE-2026-41417", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41417 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d0c8b1de-a836-59a1-b39d-87955c5c0aaa", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:870343fb-a69f-5bf8-978a-9524e790c60f", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e197232f-0150-5625-8385-18ae8625f2ba", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:15b77fbb-bcb0-5e02-8b6b-7f86652d99ec", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:45f22c7f-2220-5c18-aa35-7f8bd1c9d449", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c51c30cf-62cc-5595-95bd-41fa4a89c196", "id": "CVE-2026-42584", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42584 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:6b898781-efdd-5bb5-a607-0e2945196348", "id": "CVE-2026-42585", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42585 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:34356217-3d95-5bed-9518-69e88b14ea97", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:59db8318-f368-5d97-b2f8-3db9e0bbc686", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:33a2a234-f667-5c2b-8191-d5c6b3a12798", "id": "CVE-2026-44248", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44248 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:062e4100-742e-5c47-85af-d78aeddbb27d", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:8d674fd5-ce18-53f2-967e-962607b2541f", "id": "CVE-2026-44250", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44250 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:8f4c7d9f-83c1-59ed-91d9-8a5140f9a772", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:70d913c1-3c18-5d6d-ad75-7ad43524642a", "id": "CVE-2026-44891", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44891 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:3403d981-88e3-560d-b35e-0078b259c5c5", "id": "CVE-2026-44893", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44893 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d54e73f1-a661-5cee-b538-e1ebb5cdcb29", "id": "CVE-2026-45416", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45416 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:101c0dd1-af75-5649-bdb3-cc217151dc95", "id": "CVE-2026-45536", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45536 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:1b2af114-0eff-5daf-bd29-3497a1a38a2b", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:b372786e-f1e7-5f72-8faa-4dbfa1edd1f6", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:74a316d2-05b7-572a-9602-d412d31efad7", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:524653e1-6d39-59bf-b82d-b77b4916f047", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:78a16171-e247-5c49-81c0-6c78975f9ca6", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:9b28f9e2-2ca4-535e-9d1e-1fde1910edf5", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e75320e5-b9f9-59bb-9060-b7dd808054f6", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:34529456-e16f-5711-a951-211a1ba05441", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:eb7d8d30-5bbd-5d22-aa91-9aae07aec161", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:dd9cf346-9b0f-56ab-bcbf-e984ea16cdea", "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-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.2" } ] }, { "bom-ref": "urn:uuid:102fb598-ad28-5aae-9f23-6a851f13e9be", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:cf61c516-42d4-50cf-9f87-fa4185748b6d", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:98f3fcc5-0825-57c4-9090-ff1d5b111c9c", "id": "CVE-2026-55831", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55831 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:11c8c539-9305-52a2-8461-99853f2f379a", "id": "CVE-2026-55833", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55833 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:a8851e0c-66ec-51cb-94d1-5047014db1fe", "id": "CVE-2026-55851", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55851 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:105f3be2-2c35-5ab5-9f1c-241321ba32e5", "id": "CVE-2026-56745", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56745 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d8ee00e9-48e8-558e-85e9-766b1200bc38", "id": "CVE-2026-56746", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56746 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:ecb30a5a-85b8-5414-8ed4-6fb16ce21331", "id": "CVE-2026-56817", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56817 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e68dea62-303e-50c0-b87c-d279f8b3de2f", "id": "CVE-2026-56818", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56818 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f62af49a-2f2c-586b-85a9-88a9058dcd26", "id": "CVE-2026-56819", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56819 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:191da5dd-a785-5ad9-bec7-0112c4eadc6b", "id": "CVE-2026-56820", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56820 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:8f19ee4c-b1b9-5f68-bb74-03a9db4abf9d", "id": "CVE-2026-56821", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56821 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:500e5ac9-d1ef-5da8-8fa5-c83a90ff1abb", "id": "CVE-2026-56822", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56822 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:a9323cb0-c879-5819-b1c8-f2a5f782f2e4", "id": "CVE-2026-59898", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59898 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:81e1507d-6373-5bf4-bd0a-ef741c22e76f", "id": "CVE-2026-59899", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59899 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:06623b8e-0491-5137-a0a8-99ebb6220cf8", "id": "CVE-2026-59900", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59900 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:2b26d9a5-5959-552a-aedf-409bc251c4e1", "id": "CVE-2026-59901", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59901 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:426dd7dc-8271-51ab-894f-2dbb9f1bada5", "id": "CVE-2026-59902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59902 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:8d979ac4-efdc-5a1c-a636-f271c9c2fee5", "id": "CVE-2026-59903", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59903 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:35f42c43-49c4-5381-bdd5-e045fcad38f0", "id": "CVE-2026-59919", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59919 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:ab8b3b6c-c08a-5f2d-a044-93a6cdc6605d", "id": "CVE-2026-59920", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59920 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:fb80ca62-a57b-5d21-9f0a-a373df160154", "id": "CVE-2026-59921", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59921 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:8dba1dfc-e5bf-51f5-8529-596a9b5bbf72", "id": "CVE-2026-73507", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-73507 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:91d19834-2883-5ee9-8513-1860344c0f5f", "id": "CVE-2026-73508", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-73508 affects version 4.1.130.Final-tuxcare.2 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d15f152e-571c-50a7-b0f0-06344fdd8943", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:b642bc28-7456-5af3-b8d5-48781bbc2479", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.2" } ] }