{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:4cd5cf5c-74e2-5684-af9d-fa3c6267df19", "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.1", "type": "library", "group": "io.netty", "name": "netty-resolver-dns", "version": "4.1.130.Final-tuxcare.1", "purl": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:b69af85f-ce5d-5c39-9e5b-33dec6cdb4bf", "id": "CVE-2025-55163", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2025-55163 does not affect version 4.1.130.Final-tuxcare.1 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.1" } ] }, { "bom-ref": "urn:uuid:3f2c9f51-6d87-5d7a-92f9-8dc1557e0c84", "id": "CVE-2026-33870", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33870 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:63c1ad9d-3067-5af3-aaae-b41e7506df11", "id": "CVE-2026-33871", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-33871 is fixed in version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:c505330a-0502-5af6-86c4-933b3c105810", "id": "CVE-2026-41417", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41417 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:bef8ef49-d65f-55cf-9dbe-d1feb62242d5", "id": "CVE-2026-42578", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42578 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:00cfab64-e705-58b6-9fc5-fcd3786deee8", "id": "CVE-2026-42579", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42579 is fixed in version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:286f1b5f-3c43-5c73-bfcc-127698262d41", "id": "CVE-2026-42580", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42580 is fixed in version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:1f63ee42-1cf3-5341-85c1-80ae49a5ae82", "id": "CVE-2026-42581", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42581 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:737b8cf7-fc78-53ec-a407-304ec7e87224", "id": "CVE-2026-42583", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42583 is fixed in version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:964e3f2b-7d62-508c-bb32-d4e954efe655", "id": "CVE-2026-42584", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42584 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:e56aaa87-f66d-560b-b228-6aa2e0b728b7", "id": "CVE-2026-42585", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42585 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:86b80866-9408-518d-9edc-9e85aa4d62a4", "id": "CVE-2026-42586", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42586 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:61ad3183-dee0-522a-b898-291b30e3cbe1", "id": "CVE-2026-42587", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-42587 is fixed in version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:755ce8de-cd77-5cef-8e89-859bfc135981", "id": "CVE-2026-44248", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44248 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:3f81af85-2287-5d62-bc84-2218bb5240b8", "id": "CVE-2026-44249", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44249 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:bf09d688-afaf-5bb3-b055-d5c8bfbd7f12", "id": "CVE-2026-44250", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44250 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:78eba8c8-35be-53d5-8dd7-e5e3be3b75b2", "id": "CVE-2026-44890", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-44890 is fixed in version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:1e89363f-ee1a-52a7-8da9-268e3c4e9adb", "id": "CVE-2026-44891", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44891 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:4be77231-8648-5fbe-891a-cf39d8784e0e", "id": "CVE-2026-44893", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44893 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:9d7024a7-37b1-5afd-bfcf-47c777baf8b4", "id": "CVE-2026-45416", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45416 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:df5fb0bc-f162-57b3-8cd2-d726000df463", "id": "CVE-2026-45536", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45536 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:3ba5bb10-85cb-5913-b084-96d181229fa3", "id": "CVE-2026-45673", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45673 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:6a833712-a20c-5b5a-8da2-6aabc7a46f52", "id": "CVE-2026-45674", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45674 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:9a48eda4-68c5-5558-91e2-4bb75d227fe7", "id": "CVE-2026-46340", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-46340 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:105b9243-bb2c-5442-98a1-082bd36a20db", "id": "CVE-2026-47244", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-47244 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:9dc420c2-44c6-5a49-9cd1-58f92f8f2391", "id": "CVE-2026-47691", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-47691 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:794fc9e9-3581-5c3b-9a80-c67a6a087a4e", "id": "CVE-2026-48006", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-48006 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:c7e9b2e2-3236-5f9a-9be1-5bed1d27d158", "id": "CVE-2026-48043", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48043 is fixed in version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:a1cf57d4-fbed-56d1-9bed-2fcb4f60d5c5", "id": "CVE-2026-48059", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-48059 is fixed in version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:baa9f97d-715a-555c-867a-38822112d234", "id": "CVE-2026-50010", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50010 is fixed in version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:a0f7c2b3-bf0b-52a3-801c-f8ccdda0cc5c", "id": "CVE-2026-50011", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-50011 does not affect version 4.1.130.Final-tuxcare.1 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.1" } ] }, { "bom-ref": "urn:uuid:cb93fd96-d591-5e5e-816f-26a83f1ce4de", "id": "CVE-2026-50020", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50020 is fixed in version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:e2be7b0d-366e-5aa6-845c-1d2fb8bb0012", "id": "CVE-2026-50560", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-50560 is fixed in version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:bcf585a4-4746-56f2-962c-2edac532d993", "id": "CVE-2026-55831", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55831 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:07b6cc73-7c6a-534c-bda6-2e215e6b63fd", "id": "CVE-2026-55833", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55833 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:333e97b2-bb20-55d6-bfb5-fd74cec24f6d", "id": "CVE-2026-55851", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-55851 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:f46b7da0-f193-59de-ac58-5c88346b9381", "id": "CVE-2026-56745", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56745 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:a3549333-fcd9-5c52-8a6b-8154032bea8a", "id": "CVE-2026-56746", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56746 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:8d9e2c7b-ebbd-58a7-955f-f1bbcd3d73d1", "id": "CVE-2026-56817", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56817 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:426386e2-0810-590f-b0de-568f820c927a", "id": "CVE-2026-56818", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56818 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:5482c168-c0e5-59c3-8643-4b0c4a5f7f42", "id": "CVE-2026-56819", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56819 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:f77504b7-6ab6-50ff-bb75-05fab303d519", "id": "CVE-2026-56820", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56820 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:962e8758-694f-5d78-861f-f384d37cb298", "id": "CVE-2026-56821", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56821 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:e7af47b4-fbe7-5820-9f4a-76e66e898e24", "id": "CVE-2026-56822", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-56822 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:48947c0e-7e29-570c-ab80-53f5fbb6f1c1", "id": "CVE-2026-59898", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59898 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:b6110fb5-6856-5f98-8acc-9dd650042df5", "id": "CVE-2026-59899", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59899 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:854cfdd8-9d70-53f1-9bd2-19d51bbc344b", "id": "CVE-2026-59900", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59900 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:fb07adef-5f9a-51e9-91d9-ce113439a727", "id": "CVE-2026-59901", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59901 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:3f55b661-df5f-540b-b1d1-85f6d79af71c", "id": "CVE-2026-59902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59902 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:d552d51a-c796-54ea-b914-8dc0105357be", "id": "CVE-2026-59903", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59903 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:c428d91c-901f-5f9f-ae84-906457fac1e7", "id": "CVE-2026-59919", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59919 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:eac77367-aff4-580f-8730-af7ee89f6202", "id": "CVE-2026-59920", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59920 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:107e21d4-1e25-5b32-a051-5ec1b92e9092", "id": "CVE-2026-59921", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59921 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:fa7b719e-3a90-52b4-985a-c5725ae8e5ef", "id": "CVE-2026-73507", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-73507 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:4ef8090c-ccf1-5c98-82ea-0ab2e411811b", "id": "CVE-2026-73508", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-73508 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:b450fd53-9918-5a49-9cf0-1a72bc38bc23", "id": "GHSA-mfg7-5gfp-c4w3", "analysis": { "state": "exploitable", "detail": "Vulnerability GHSA-mfg7-5gfp-c4w3 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }, { "bom-ref": "urn:uuid:76288375-1160-59b5-89d1-6e4605163860", "id": "GHSA-v74w-7mr3-4qg3", "analysis": { "state": "exploitable", "detail": "Vulnerability GHSA-v74w-7mr3-4qg3 affects version 4.1.130.Final-tuxcare.1 of io.netty:netty-resolver-dns." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-resolver-dns@4.1.130.Final-tuxcare.1" } ] }