{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:95fdf3d2-718a-58e7-95f2-b2c72ece236a", "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.3", "type": "library", "group": "io.netty", "name": "netty-codec-haproxy", "version": "4.1.130.Final-tuxcare.3", "purl": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:e3108151-b3b9-5214-9b03-01a54be9d576", "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-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.3" } ] }, { "bom-ref": "urn:uuid:0d46cda0-bf3c-514b-a855-c54f89c71936", "id": "CVE-2026-33870", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-33870 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:6354a74f-2e52-56f3-b958-538bf934eb3e", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:9cbfc279-2e41-58e5-beba-14e5f2165741", "id": "CVE-2026-41417", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-41417 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:7bba0a75-c882-5712-a66f-bd332accb425", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:077e7422-6c3d-5bfc-937a-34f9b95a0a22", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:c7e23204-0cce-5a0b-8726-0cce10daf414", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:4eec7e3b-f91a-5d1c-b7c0-133236fe0796", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1422649b-e718-5fb0-b76b-e9f324ba55b0", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:71407afb-88eb-5374-a1a2-8539749e2a66", "id": "CVE-2026-42584", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42584 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:541a90d0-5715-57c8-bc49-8304e0a623f6", "id": "CVE-2026-42585", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-42585 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:04d735e5-c2b1-591f-8bfc-25bed9d8e0ee", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:6a194e2f-41c8-5631-9d19-6523b570f246", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:3f2eb783-7d64-57e5-be89-b019db06ca0f", "id": "CVE-2026-44248", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44248 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:aa4456f2-4ea5-55e5-bce9-3e85e2b0d0eb", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d25a993c-2db7-5073-930f-fc5f819d535d", "id": "CVE-2026-44250", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44250 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:398edfd9-34d1-5420-8d3b-9eae91036831", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d77e9f53-cfda-5d96-af08-0d745959628d", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:001a4a99-af42-5034-b631-62f16294286f", "id": "CVE-2026-44893", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-44893 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:363fe75d-de26-5918-a3c9-00e98f6a3677", "id": "CVE-2026-45416", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45416 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:80b77a3f-e505-5926-880e-66e99db4abba", "id": "CVE-2026-45536", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-45536 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:8b1c29de-716c-53e2-97b7-0b1726c45050", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1248028c-90e8-5a77-ba65-54b10c0342a0", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f3347e4c-9f84-502a-99d1-9a8c85bedcca", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e3839da4-5723-5261-b1fd-5350cbd512ec", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:8ad190dd-cc1d-5392-9b4a-96554489e486", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:c244db63-fbcb-5533-8816-cceea6725abe", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f2c72991-6dab-5e20-8afd-d5657d5b9cc4", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:9c9209d7-6024-5bce-999e-c284d28ec7aa", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:b2a249c1-1d77-568a-89ea-fbfa2cd4b029", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:3348084e-79e1-536f-82df-f047893eef6d", "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-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.3" } ] }, { "bom-ref": "urn:uuid:07d999fe-d80a-5cb3-b0f0-9a2c8c96add9", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:af911f9d-a319-5fe8-81c8-52dc9de45815", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:674cbb1a-efdf-5c0d-86ab-92aeb0fa25fb", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d92e4dae-aaa3-5a1c-9c1f-a8fd6c9df829", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:c739a600-f1f4-558a-bbb3-e0e6cdcfd3a5", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:17bc7a1d-e1b8-56c5-8966-919c35449b97", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:91d05198-cfbd-5365-a05b-9dc65c799b57", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:81dddac5-dc0f-5aa8-859e-3ad84b2e3b42", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:3d63964e-9f16-578b-af4c-8ba5b59b174d", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:0d71db5a-469f-5c8f-b350-d564b62b9288", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:c6d970c0-7e05-53bf-a1ea-78692006cde8", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1505cee3-0bbf-5098-9fd7-57cf727bcb70", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:5cc0e65e-a2cd-586c-b8e2-99c337243cba", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:84f7c4e9-15a5-5338-9345-c3d5479e07e3", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:beb1a933-bb94-5606-9e38-d2b11b4367ac", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:f4c164dc-d991-5766-9c84-aa282585dfad", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:5127f5a0-339f-5352-b996-2e3d0c859ec9", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:5aa5e7d6-e50b-5680-b7a1-937dd5830edd", "id": "CVE-2026-59902", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59902 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:a2b40935-8734-5631-a4ed-cccf76376160", "id": "CVE-2026-59903", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-59903 affects version 4.1.130.Final-tuxcare.3 of io.netty:netty-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:9cfdcdfb-3cac-55da-b7a2-43b69231dbd2", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e7bf4af7-1b70-58b5-a781-f8cd78d32fc1", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d0b7d746-0c8a-58c2-9ddb-ec9e34d77e7a", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:d8af3519-529e-537a-b13e-d2d13247b9f1", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:12ab9f43-5a96-5a95-a7ef-d149f756c3ba", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:4b665e94-63b1-5030-9f78-25817e7bc5a1", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:4cdb6430-82d1-5d96-b897-c136306482c0", "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-codec-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.3" } ] }