{ "@id": "urn:uuid:6ec20d0d-a93b-4efb-b3a5-74ab41c1e274", "role": "Document Creator", "author": "https://tuxcare.com", "version": 19, "@context": "https://openvex.dev/ns/v0.2.0", "timestamp": "2026-10-31T11:37:00.140949+00:00", "statements": [ { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-29T00:16:38.201074+00:00", "status_notes": "Vulnerability CVE-2014-0193 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2014-0193" }, "action_statement": "Vulnerability CVE-2014-0193 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-29T10:21:18.524281+00:00", "status_notes": "Vulnerability CVE-2014-3488 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2014-3488" }, "action_statement": "Vulnerability CVE-2014-3488 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T23:00:15.311032+00:00", "status_notes": "Vulnerability CVE-2016-4970 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2016-4970" }, "action_statement": "Vulnerability CVE-2016-4970 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T22:44:11.275398+00:00", "status_notes": "Vulnerability CVE-2019-16869 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2019-16869" }, "action_statement": "Vulnerability CVE-2019-16869 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T23:33:09.807961+00:00", "status_notes": "Vulnerability CVE-2019-20444 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2019-20444" }, "action_statement": "Vulnerability CVE-2019-20444 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T23:00:15.311032+00:00", "status_notes": "Vulnerability CVE-2019-20445 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2019-20445" }, "action_statement": "Vulnerability CVE-2019-20445 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-29T00:12:47.728703+00:00", "status_notes": "Vulnerability CVE-2020-11612 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2020-11612" }, "action_statement": "Vulnerability CVE-2020-11612 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-29T03:28:09.355486+00:00", "status_notes": "Vulnerability CVE-2020-7238 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2020-7238" }, "action_statement": "Vulnerability CVE-2020-7238 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T23:33:09.807961+00:00", "status_notes": "Vulnerability CVE-2021-21290 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2021-21290" }, "action_statement": "Vulnerability CVE-2021-21290 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2021-21295 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2021-21295" }, "action_statement": "Vulnerability CVE-2021-21295 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T23:49:59.024011+00:00", "status_notes": "Vulnerability CVE-2021-21409 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2021-21409" }, "action_statement": "Vulnerability CVE-2021-21409 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T22:54:14.665991+00:00", "status_notes": "Vulnerability CVE-2021-37136 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2021-37136" }, "action_statement": "Vulnerability CVE-2021-37136 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T22:54:14.665991+00:00", "status_notes": "Vulnerability CVE-2021-37137 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2021-37137" }, "action_statement": "Vulnerability CVE-2021-37137 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T23:33:09.807961+00:00", "status_notes": "Vulnerability CVE-2021-43797 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2021-43797" }, "action_statement": "Vulnerability CVE-2021-43797 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T23:33:09.807961+00:00", "status_notes": "Vulnerability CVE-2022-24823 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2022-24823" }, "action_statement": "Vulnerability CVE-2022-24823 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-31T08:52:10.620905+00:00", "status_notes": "Vulnerability CVE-2022-41881 does not affect version 4.1.122.Final-tuxcare.4 of io.netty:netty-all. not_affected \u2014 The target version 4.1.122.Final is not affected by CVE-2022-41881. The fix for the infinite recursion vulnerability in HAProxy TLV parsing was already present in the upstream Netty release 4.1.122.Final that was onboarded to the TuxCare repository. The fix (commit cd91cf3c99 by Norman Maurer) adds a MAX_NESTING_LEVEL limit of 128 and checks it before recursion in readNextTLV(), preventing Stac...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2022-41881" }, "impact_statement": "not_affected \u2014 The target version 4.1.122.Final is not affected by CVE-2022-41881. The fix for the infinite recursion vulnerability in HAProxy TLV parsing was already present in the upstream Netty release 4.1.122.Final that was onboarded to the TuxCare repository. The fix (commit cd91cf3c99 by Norman Maurer) adds a MAX_NESTING_LEVEL limit of 128 and checks it before recursion in readNextTLV(), preventing Stac..." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-29T01:45:14.642108+00:00", "status_notes": "Vulnerability CVE-2022-41915 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2022-41915" }, "action_statement": "Vulnerability CVE-2022-41915 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T22:15:27.793370+00:00", "status_notes": "Vulnerability CVE-2023-34462 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2023-34462" }, "action_statement": "Vulnerability CVE-2023-34462 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-29T10:21:18.524281+00:00", "status_notes": "Vulnerability CVE-2023-4586 is a false positive for io.netty:netty-all 4.1.122.Final-tuxcare.4.", "vulnerability": { "name": "CVE-2023-4586" }, "impact_statement": "The vulnerability has been withdrawn." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T22:21:49.480044+00:00", "status_notes": "Vulnerability CVE-2024-29025 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2024-29025" }, "action_statement": "Vulnerability CVE-2024-29025 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-31T11:23:00.236792+00:00", "status_notes": "Vulnerability CVE-2024-47535 does not affect version 4.1.122.Final-tuxcare.4 of io.netty:netty-all. not_affected \u2014 CVE-2024-47535 is NOT present in the target. The upstream fix (commit fbf7a704a8 by Norman Maurer) was already included in Netty 4.1.122.Final when TuxCare onboarded this version. The fix introduces BoundedInputStream to limit bytes read from files during initialization (default 8KB, 1MB for resolv.conf), preventing the denial-of-service attack where an attacker places a massive file at predict...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2024-47535" }, "impact_statement": "not_affected \u2014 CVE-2024-47535 is NOT present in the target. The upstream fix (commit fbf7a704a8 by Norman Maurer) was already included in Netty 4.1.122.Final when TuxCare onboarded this version. The fix introduces BoundedInputStream to limit bytes read from files during initialization (default 8KB, 1MB for resolv.conf), preventing the denial-of-service attack where an attacker places a massive file at predict..." }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T22:15:27.793370+00:00", "status_notes": "Vulnerability CVE-2025-24970 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2025-24970" }, "action_statement": "Vulnerability CVE-2025-24970 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-31T11:37:00.140949+00:00", "status_notes": "Vulnerability CVE-2025-25193 does not affect version 4.1.122.Final-tuxcare.4 of io.netty:netty-all. not_affected \u2014 The target Netty 4.1.122.Final is not affected by CVE-2025-25193. The vulnerable code pattern (null bytes bypassing read limits in BoundedInputStream) was already fixed in the upstream Netty 4.1.122.Final release before TuxCare onboarded it. The fix (commit d1fbda62d3a by norman_maurer@apple.com, dated 2025-02-10) changed the byte-counting condition from `if (b > 0)` to `if (b != -1)`, ensuring...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2025-25193" }, "impact_statement": "not_affected \u2014 The target Netty 4.1.122.Final is not affected by CVE-2025-25193. The vulnerable code pattern (null bytes bypassing read limits in BoundedInputStream) was already fixed in the upstream Netty 4.1.122.Final release before TuxCare onboarded it. The fix (commit d1fbda62d3a by norman_maurer@apple.com, dated 2025-02-10) changed the byte-counting condition from `if (b > 0)` to `if (b != -1)`, ensuring..." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-55163 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2025-55163" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-58056 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2025-58056" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-58057 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2025-58057" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-59419 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2025-59419" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2025-67735 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2025-67735" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-33870 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-33870" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-33871 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-33871" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-41417 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-41417" } }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-42577 does not affect version 4.1.122.Final-tuxcare.4 of io.netty:netty-all. CVE-2026-42577 affects Netty 4.2.x only (advisory range >= 4.2.0.Final, < 4.2.13.Final). An fd left registered with an epoll event mask of 0 is woken forever by the unmaskable EPOLLERR/EPOLLHUP after a RST on a half-closed connection. Target 4.1.122.Final is NOT affected due to architectural differences. The patch modifies EpollIoHandler.java and EpollIoOps.java, part of 4.2's IoHandler/IoOps abstraction. Neither file exists in 4.1.x, which registers via EpollEventLoop.modify() off AbstractEpollChannel.flags. That field is seeded Native.EPOLLET, and no read/close/half-close path clears it (only the explicit pre-registration setEpollMode(LEVEL_TRIGGERED) opt-in), so the registration stays edge-triggered and the RST is reported once per edge instead of on every epoll_wait. The chain from INPUT (connection state change) to GOAL (CPU busy-loop via empty event mask) is broken at step (ii): the target cannot produce an empty event mask. Verdict: not_affected. Justification: code_not_reachable (Rule 5 Type A2).", "justification": "vulnerable_code_not_in_execute_path", "vulnerability": { "name": "CVE-2026-42577" }, "impact_statement": "CVE-2026-42577 affects Netty 4.2.x only (advisory range >= 4.2.0.Final, < 4.2.13.Final). An fd left registered with an epoll event mask of 0 is woken forever by the unmaskable EPOLLERR/EPOLLHUP after a RST on a half-closed connection. Target 4.1.122.Final is NOT affected due to architectural differences. The patch modifies EpollIoHandler.java and EpollIoOps.java, part of 4.2's IoHandler/IoOps abstraction. Neither file exists in 4.1.x, which registers via EpollEventLoop.modify() off AbstractEpollChannel.flags. That field is seeded Native.EPOLLET, and no read/close/half-close path clears it (only the explicit pre-registration setEpollMode(LEVEL_TRIGGERED) opt-in), so the registration stays edge-triggered and the RST is reported once per edge instead of on every epoll_wait. The chain from INPUT (connection state change) to GOAL (CPU busy-loop via empty event mask) is broken at step (ii): the target cannot produce an empty event mask. Verdict: not_affected. Justification: code_not_reachable (Rule 5 Type A2)." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-42578 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-42578" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-42579 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-42579" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-42580 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-42580" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-42581 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-42581" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-42583 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-42583" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-42584 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-42584" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-42585 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-42585" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-42586 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-42586" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-42587 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-42587" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-44248 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-44248" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-44249 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-44249" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-44250 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-44250" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-44890 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-44890" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-44891 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-44891" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-44893 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-44893" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-45416 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-45416" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-45536 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-45536" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-45673 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-45673" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-45674 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-45674" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-46340 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-46340" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-47244 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-47244" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-47691 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-47691" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-48006 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-48006" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-48043 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-48043" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-48059 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-48059" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-50010 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-50010" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-50011 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-50011" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-50020 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-50020" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-50560 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-50560" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-55831 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-55831" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-55833 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-55833" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-55851 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-55851" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-56745 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-56745" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-56746 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-56746" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-56817 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-56817" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-56818 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-56818" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-56819 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-56819" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-56820 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-56820" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-56821 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-56821" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-56822 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-56822" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-59898 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-59898" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-59899 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-59899" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-59900 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-59900" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-59901 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-59901" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-59902 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-59902" } }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-59903 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-59903" }, "action_statement": "Vulnerability CVE-2026-59903 affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-59919 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-59919" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-59920 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-59920" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-59921 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-59921" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-73507 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-73507" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-73508 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-73508" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-75595 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-75595" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability CVE-2026-75596 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "CVE-2026-75596" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability GHSA-mfg7-5gfp-c4w3 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "GHSA-mfg7-5gfp-c4w3" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-09-24T09:31:26.931840+00:00", "status_notes": "Vulnerability GHSA-v74w-7mr3-4qg3 is fixed in version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "GHSA-v74w-7mr3-4qg3" } }, { "status": "affected", "products": [ { "@id": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4", "identifiers": { "purl": "pkg:maven/io.netty/netty-all@4.1.122.Final-tuxcare.4" } } ], "timestamp": "2026-10-28T22:15:27.793370+00:00", "status_notes": "Vulnerability GHSA-xpw8-rcwv-8f8p affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all.", "vulnerability": { "name": "GHSA-xpw8-rcwv-8f8p" }, "action_statement": "Vulnerability GHSA-xpw8-rcwv-8f8p affects version 4.1.122.Final-tuxcare.4 of io.netty:netty-all." } ] }