{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:4776de4b-d1c7-5372-8aa2-6776e1dbe2af", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2", "type": "library", "group": "io.netty", "name": "netty-codec-haproxy", "version": "4.1.130.Final-tuxcare.2", "purl": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:639afb01-ed05-5667-903e-14e2973a7728", "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-haproxy. 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-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:259eeb27-5704-55bf-aad3-ac3db029e3df", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:64ab187b-1d05-527a-88b2-afd2099ee2f8", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e65ae066-fe25-54ec-a6bb-f3ac63da6fe1", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4c1b91dd-7f5c-5e8c-a4f2-28d851de1127", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:611637e8-fcaa-544f-88ea-623f076ca8fe", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4de3ea6a-5b1e-5f3b-8ad0-205ce16a45c8", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:4880d6d1-6d60-5ab6-8ded-c2677684d2c9", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e43f45e5-804b-5de1-b7e0-f37d8339270b", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:8fbf74b8-1ba7-5bbb-a556-2bcb36ecd79f", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:7ceb051a-fdc5-5360-a1ef-9a897c84304c", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e0944172-1475-5d18-bf25-58ad299687a1", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:576f1004-e93f-55f4-b04e-7f1782fa3065", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:a924727c-a92b-5b1d-87cd-2972dac79fd5", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e4ace8fe-b509-59a5-b664-7a1a624db8c2", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:6fe10c94-02df-5ed5-98cd-a1cd1924b5d7", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:cc1efc84-1af2-5158-950a-cb043499306d", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:e6864612-d99a-5058-91de-b7b69b3cf7ce", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:296f1aa9-690e-503e-943a-b09e580e128b", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:198ea4d4-2482-5293-9b06-14be58cace0d", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:29f7c637-591f-58b4-a138-c11830be6ec9", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:fea23097-0343-57f0-b513-9ec811e6556c", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f798e859-4671-5116-bdf6-330ff02cf721", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:d01729a2-3d59-5e7a-aed0-20c0369f3200", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:0d28bffa-bed6-55e5-a0d9-c394baae411d", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:ef39409f-5c69-5eff-b539-16616562d030", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:efd1d5bf-26bd-5538-9b29-5d392b25fc89", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:87c92fc2-98ce-544f-9f54-9c9d17f2bd31", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:9a647458-4cf9-50ae-9f64-56671c7e84cb", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c361378d-0446-5b2d-a0e1-de3ba5ee14e9", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:8be91de9-0e42-53bc-8251-1ed3e047d468", "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-haproxy. 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-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:313c4f41-9fe2-5941-b6f7-16c2afd5d946", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:38ab4009-ad78-5816-8b8c-cba806c0f049", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:b5298c18-eb06-5137-811d-5b8960c85a93", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f1cc3bb2-847a-5550-a386-f7376d8e4fef", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:6bc5cb0a-2a57-5e03-be1f-aa177acab5ac", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:a7031516-f1dd-5b85-b6e7-faff09dc2b21", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:ee28008b-ad51-59d9-baf1-c3e28162c773", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:b6a5a1ab-7ab7-523c-8616-52b42d7fcb30", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:5ceec799-a4a3-5f9c-9b57-2639aeff6daa", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:385e09ab-1863-568a-bb5a-64639065cf91", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f1296d63-595d-5751-9b0a-ac4104d3fe4c", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:bb62ab60-6f92-5213-94da-ef8e995d6e9e", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:024d5796-208e-56ce-b6d8-efea35e67ca7", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:b558b910-e7f8-5d22-84d7-95a4538b19f3", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:c6d4e22c-5f4a-5c29-bcfa-65ed447a2556", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:2184ff13-f41d-5510-a99d-4ee422658119", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:ed055860-925e-56a8-a5d5-7c628997c187", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:887e67cf-cd08-5d1b-8ec0-e1add27291f1", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:f40f9c84-a79c-5bb7-8770-e961f05f570e", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:0bf1b9ee-a426-5ef3-ae29-50afd03d4f76", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:5f18e0c8-01be-5c6b-82d6-b3c05afd5367", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:373dd611-6c4b-5ea9-a180-162418f8e868", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:17aad310-8a06-5513-a509-78faad074124", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:b5ac2c04-7f68-5d50-9198-491f802e4678", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:07815b68-b916-521d-8ef8-1fd1f4b2c9df", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }, { "bom-ref": "urn:uuid:3753e478-f398-548d-930e-35e74e91e5f2", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.2" } ] }