{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:926ac0fc-3208-571a-9cc8-ce643170a587", "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.4", "type": "library", "group": "io.netty", "name": "netty-codec-dns", "version": "4.1.130.Final-tuxcare.4", "purl": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:5d7c0de6-c7b5-505f-8533-c475d95be313", "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-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.4" } ] }, { "bom-ref": "urn:uuid:c4c74cba-2159-553c-82c2-3823888b6034", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5e0edad4-64a0-5b4a-a172-520689017bad", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6cc21426-1203-57f3-a36c-98a9256ff068", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b82badf1-1c9f-505c-b2d6-1209be07e37f", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:09a62924-903a-5fbc-93b8-4dca27ec4f71", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:df85fd94-fd0e-5e5f-bde2-7f7708274edb", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:dcadbcb0-ed6c-5e2c-8426-5f73dd17214c", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:12194dae-110e-5d8e-b769-e1bcf838ae81", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a5496426-d3fa-5978-90c2-5d81c82f500b", "id": "CVE-2026-42584", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42584 affects version 4.1.130.Final-tuxcare.4 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d7b5eb4c-0355-5fae-a481-b2a267b1fd01", "id": "CVE-2026-42585", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42585 affects version 4.1.130.Final-tuxcare.4 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:745de4ae-3328-5335-a1af-c52d1ae3e08d", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:98c4c1db-fc92-5d62-a3b9-04809ef98062", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a9001e06-3308-5d46-b715-c704488458b1", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4224c072-7a63-5924-adaf-48f17bc5b4ad", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d0a3c315-5efe-5664-949a-09162edbbc91", "id": "CVE-2026-44250", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44250 affects version 4.1.130.Final-tuxcare.4 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ccdd3037-781e-5852-a0da-d4fa9b191e07", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a0f5aa87-4a2f-5008-8e4e-33746dae12a9", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1681bc04-709e-5729-a83d-f8960ad033a2", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b199e0a1-385f-5f22-8a2c-7d814bcbbd1e", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:0f2c659d-2620-55c4-b948-a01c8e6be5d8", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:af121d39-a65a-58a9-914b-9d13806c85b6", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c6aa33ff-91bf-5fe3-aeb0-24bf658fb0a6", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:2b76fafe-b9ab-55bd-bd0c-f25b98cc5922", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ab633f13-962d-5c00-a8ec-106b78a32ec7", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a0548f4c-96e3-5e01-85ab-b3f5b80471f3", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ddc90972-b4ea-5fce-8348-8ca64356f930", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5f434480-149d-51c1-8e4c-775aac467d99", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:85719716-4abe-5f45-bb3f-c42213630ba4", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f49daa72-c093-5ff7-9935-c605f29ac59b", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e3778141-89ca-56f5-bd86-4e5e4ac9a24a", "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-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.4" } ] }, { "bom-ref": "urn:uuid:21e37f97-762e-586e-8732-59370abee6e4", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3434387e-fd3f-5b4f-baa5-52ebeb36d0a4", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8952bf33-7a6e-5951-9494-da84bb183a3e", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b467d5e1-89b1-5fdd-ad26-7526f57cea10", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:de4a12f2-2f8e-5fe3-9b3e-3cc8df5042d3", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:f5192936-dc9e-556f-9cac-7fd50f5c0021", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:37b4db71-67f6-5432-8612-17cf84ce5849", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:79d0ee3c-23e5-557e-b971-49bdfcc077a8", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4323c657-6cb8-5d2f-8fb5-ca050e0bcbf4", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:44085fe8-9bca-51a3-8ec2-beb88198f120", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:047b5428-9c9b-5c4a-a0ff-6859c27fe24f", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d4671b32-f49b-5216-864c-a33cff5d99c0", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:2ef39afa-bfb3-5e54-b0e9-b8d097f33b90", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b38ebcd5-235d-5210-9a8b-32f61c8ff4bf", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:9006c1ec-8ad3-5d22-919c-320d65a97d35", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:43d08ad4-3e66-50f4-901a-dc53d9cce870", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:22ed81a1-e192-5213-880d-dbea4f472f6c", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5b306190-e0c2-5673-a93c-575aa7b10afe", "id": "CVE-2026-59902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59902 affects version 4.1.130.Final-tuxcare.4 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:39c2dda4-be42-5eca-834e-4631feef8e11", "id": "CVE-2026-59903", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59903 affects version 4.1.130.Final-tuxcare.4 of io.netty:netty-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:44b42f88-fcf2-5c5e-862f-173c5d295337", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:21cbfee1-61f8-5b5c-9786-5c680a3b9ab6", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e854f1ac-297b-522d-89e3-aee45a0466fb", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:fdd083b3-fbc6-5479-a04a-a32129db9d26", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:94796172-e96e-5d21-953a-7fe34c292c55", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d28c7767-b181-5e8c-a9be-8870c9932da3", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7c06d47a-89a5-5192-8774-3cfaee7d1222", "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-codec-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-codec-dns@4.1.130.Final-tuxcare.4" } ] }