{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:2dc1061a-aa47-5306-bd7b-ba76ddc36e0d", "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.4", "type": "library", "group": "io.netty", "name": "netty-codec-haproxy", "version": "4.1.130.Final-tuxcare.4", "purl": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:cc4953e0-19f8-556d-8753-7ba012dd4e18", "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-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.4" } ] }, { "bom-ref": "urn:uuid:9dfb25b3-da48-5357-983e-9a730a07b4c9", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:47a98f03-110a-5608-8624-06fd8820499b", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:89765e6f-132e-57b7-b55d-ef165ef03ce0", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:23cbee8f-d1ea-5dfd-b2eb-b8474b83438f", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:57cec866-b896-5cf7-a245-a6c2d07ca0d5", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e37d47e8-dff0-5270-951d-4a39bcb8dc54", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1a532da6-2228-5344-9ca8-f129356e2fe9", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:af52a538-d62d-588d-b326-73b2f6a7a78e", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5d3f6306-f735-5cb1-99de-84bb8e2449fa", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:458ca9e0-c472-5806-9c75-5a63f3c03fda", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:2bf266a9-d8e2-5442-a779-f7f27ccbd7d6", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3fef60f0-471f-53c1-b232-cbcd77f3ba0e", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:1b85e042-5f62-53c9-bdf7-635c392bb560", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c9b662f7-1c58-5ea3-b18b-bf54f31f03f8", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c49b2ba5-6af3-5d69-8123-3f89f6b03fdf", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:2fcbbccf-9845-5aba-8f8f-81fd028a5d52", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:924e4ea5-ee4a-5751-889d-40c1b54329b7", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:7a122c5e-9aeb-5716-b6e9-ab50a816e0b5", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:60a6b878-05b4-5928-a66e-464bd2ed3bef", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a89dedb9-1ea6-5f69-bdab-921f748ede3f", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:80b7af0c-5800-5e43-95ec-ad6f8cb4bbd6", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:76cdb3b6-191f-5dcf-85a8-38f0e69150a4", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:dd4b319a-2d88-57dd-91a2-c94ef0a9debf", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:60d584af-c1f8-5908-b869-02af07879330", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:81574ee8-376c-5810-b6dc-4ef78176cc4f", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e48a7ae8-7f72-5a52-ac61-c7ce9391bce6", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:812ebf50-c400-57e2-9c02-f2466f81070a", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4d5da85c-84d6-55f1-94ee-2511f9bfe8ea", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6712a263-c524-5359-aa21-6840910aaf54", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a0b51d00-44b2-5acc-99f9-dc763eb449bb", "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-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.4" } ] }, { "bom-ref": "urn:uuid:ea00fe9a-95f1-5032-8ab1-895100bf33be", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b997b8b7-e5f1-5a18-8d22-ee4a32b930d0", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:0670b7ba-a8a6-57f5-b27f-d15009405e52", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5f84ae21-6ea0-5699-80f7-b152b464a208", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a7c048e4-db97-5ba0-ac08-84d3370c6ef4", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:6e65e2f2-c971-5573-be23-289827b55c92", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:504f3a15-ae9d-5de7-ac99-0fc5e1d40d81", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:c6cd6121-9bce-5032-b992-417355e3cf3d", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:a538ee45-ab8e-53a2-a303-b91e96997c65", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:fd627b41-1875-5ebc-89af-b7b5d82a3e9d", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5f548e8b-f782-59de-91bc-91630683bf3d", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:4a6e18e6-4d25-585a-b2b9-fa48d5ee1c05", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:e5a85297-d5dc-551b-ba67-c35e8cea70c5", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:b88a7371-01b9-5ec3-9ddf-6743979f63b5", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:3eb6b113-84e7-5a2d-b873-796c2ac96f98", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:02879b3d-f1d3-5544-bfaa-182776ffb1bb", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5950eb18-8d48-5d78-8b2d-36bb087144ef", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:61e55208-a7fb-5b1c-bb43-c7087aa7bf0a", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:ead42796-70cf-5978-b9e2-4ff4b4bf6df5", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:d89007b5-9998-5944-bfaa-abc292929206", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:caac5f8d-3413-5b6b-ae2b-8244d9e3a924", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:263aba9e-9d51-5186-a2cf-074f89ff5882", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:8ca47871-a8f3-5bba-913e-a0453aa24641", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:5356900b-232e-5f8a-a774-66cdfaf6efff", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:bb0005d9-0e22-5c4c-9fbb-b5e8c13ad700", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }, { "bom-ref": "urn:uuid:cc58cc66-a1b5-51ad-8cb5-2aed6e1befab", "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-haproxy." }, "affects": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] } ], "dependencies": [ { "ref": "pkg:maven/io.netty/netty-codec-haproxy@4.1.130.Final-tuxcare.4" } ] }