Vulnerabilities
Recent vulnerabilities
Recent vulnerabilities from
Select from 70 available sources using the dropdown above.
| ID | Description | Published | Updated |
|---|---|---|---|
| cleanstart-2026-wa48911 | authenticated SSH client that repeatedly opened channels which were rejected by the server caused unbounded memory growth, eventually crashing the server process and affecting all connected users | 2026-06-11T00:51:16.571546Z | 2026-06-10T14:18:06Z |
| cleanstart-2026-kv53168 | Decoding a maliciously-crafted MIME header containing many invalid encoded-words can consume excessive CPU | 2026-06-11T00:37:12.717829Z | 2026-06-10T12:58:45Z |
| cleanstart-2026-lo88261 | Within HostnameError | 2026-06-11T00:37:42.858635Z | 2026-06-10T12:54:57Z |
| cleanstart-2026-gu65783 | Within HostnameError | 2026-06-11T00:37:42.823413Z | 2026-06-10T12:53:55Z |
| cleanstart-2026-nm83456 | AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python | 2026-06-11T00:58:47.477773Z | 2026-06-10T12:40:12Z |
| cleanstart-2026-kn74022 | Decoding a maliciously-crafted MIME header containing many invalid encoded-words can consume excessive CPU | 2026-06-11T00:37:42.722881Z | 2026-06-10T12:36:28Z |
| cleanstart-2026-jy46135 | Security fixes for ghsa-m5vv-6r4h-3vj9 applied in versions: 0.12.0-r3 | 2026-06-11T00:37:43.592316Z | 2026-06-10T12:33:26Z |
| cleanstart-2026-hw72470 | Security fixes for ghsa-72hv-8253-57qq applied in versions: 3.6.4-r4 | 2026-06-11T00:40:14.004644Z | 2026-06-10T11:02:26Z |
| cleanstart-2026-gb30250 | Security fixes for ghsa-72hv-8253-57qq, ghsa-qqpg-mvqg-649v applied in versions: 3.9.4-r0, 3.9.4-r6 | 2026-06-11T00:37:44.484382Z | 2026-06-10T11:02:26Z |
| cleanstart-2026-cc73064 | In Eclipse Jetty, the HTTP/1 | 2026-06-11T00:40:13.261602Z | 2026-06-10T11:02:26Z |
| cleanstart-2026-ao11810 | Netty is an asynchronous, event-driven network application framework | 2026-06-11T00:41:43.575059Z | 2026-06-10T11:02:26Z |
| cleanstart-2026-ok35650 | During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succ... | 2026-06-11T00:41:13.291496Z | 2026-06-10T10:37:02Z |
| cleanstart-2026-bm78291 | Decoding a maliciously-crafted MIME header containing many invalid encoded-words can consume excessive CPU | 2026-06-11T00:59:17.738426Z | 2026-06-10T10:16:46Z |
| cleanstart-2026-sq76279 | Decoding a maliciously-crafted MIME header containing many invalid encoded-words can consume excessive CPU | 2026-06-11T00:58:17.245789Z | 2026-06-10T10:10:23Z |
| cleanstart-2026-eg39405 | Netty is an asynchronous, event-driven network application framework | 2026-06-11T01:01:54.682665Z | 2026-06-10T07:43:19Z |
| cleanstart-2026-sa78596 | Security fixes for CVE-2025-47911, CVE-2025-47912, CVE-2025-58183, CVE-2025-58185, CVE-2025-58186, CVE-2025-58187, CVE-2025-58188, CVE-2025-58189, CVE-2025-61723, CVE-2025-61724, CVE-2025-61725, CVE-2025-61732, CVE-2026-27139, CVE-2026-27140, CVE-2026-27145, CVE-2026-32280, CVE-2026-32281, CVE-2026-32282, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289, CVE-2026-33810, CVE-2026-33811, CVE-2026-33814, CVE-2026-35469, CVE-2026-39820, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39836, CVE-2026-42499, CVE-2026-42504, CVE-2026-42507, ghsa-pc3f-x583-g7j2 applied in versions: 1.34.1-r0, 1.34.1-r2, 1.34.1-r3, 1.34.1-r4, 1.34.1-r5, 1.34.1-r6 | 2026-06-08T12:33:52.277127Z | 2026-06-05T11:01:01Z |
| cleanstart-2026-qu97327 | Security fixes for CVE-2025-61726, CVE-2025-61727, CVE-2025-61728, CVE-2025-61729, CVE-2025-61730, CVE-2025-61731, CVE-2025-61732, CVE-2025-68119, CVE-2025-68121, CVE-2026-25679, CVE-2026-27139, CVE-2026-27140, CVE-2026-27142, CVE-2026-27143, CVE-2026-27144, CVE-2026-32280, CVE-2026-32281, CVE-2026-32282, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289, CVE-2026-33811, CVE-2026-33814, CVE-2026-39817, CVE-2026-39819, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39836, CVE-2026-42499, CVE-2026-42501 applied in versions: 1.5.1-r0, 1.5.1-r1 | 2026-06-08T12:42:21.493198Z | 2026-06-05T10:00:04Z |
| cleanstart-2026-pu75130 | Security fixes for CVE-2026-27140, CVE-2026-32280, CVE-2026-32281, CVE-2026-32282, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289, CVE-2026-33810, CVE-2026-33811, CVE-2026-33814, CVE-2026-35469, CVE-2026-39817, CVE-2026-39819, CVE-2026-39820, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39836, CVE-2026-42499, CVE-2026-42501, ghsa-pc3f-x583-g7j2 applied in versions: 2.19.2-r0, 2.19.2-r1, 2.19.2-r2, 2.19.2-r3 | 2026-06-08T12:36:40.099271Z | 2026-06-05T10:00:04Z |
| cleanstart-2026-pq10269 | Security fixes for CVE-2025-61726, CVE-2025-61727, CVE-2025-61728, CVE-2025-61729, CVE-2025-61730, CVE-2025-61731, CVE-2025-61732, CVE-2025-68121, CVE-2026-25679, CVE-2026-27139, CVE-2026-27140, CVE-2026-27142, CVE-2026-27143, CVE-2026-27144, CVE-2026-32280, CVE-2026-32281, CVE-2026-32282, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289, CVE-2026-33810, CVE-2026-33811, CVE-2026-33814, CVE-2026-39817, CVE-2026-39819, CVE-2026-39820, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39836, CVE-2026-42499, CVE-2026-42501 applied in versions: 1.5.1-r0, 1.5.1-r1, 1.5.1-r2 | 2026-06-08T12:37:56.392664Z | 2026-06-05T10:00:04Z |
| cleanstart-2026-on25409 | Security fixes for CVE-2026-25679, CVE-2026-27140, CVE-2026-32280, CVE-2026-32281, CVE-2026-32283, CVE-2026-32289 applied in versions: 1.13.1-r1, 1.13.2-r0, 1.13.2-r1 | 2026-06-08T12:35:46.342723Z | 2026-06-05T10:00:04Z |
| cleanstart-2026-rq86436 | Security fixes for CVE-2026-25679, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-27139, CVE-2026-27140, CVE-2026-27142, CVE-2026-27143, CVE-2026-32280, CVE-2026-32281, CVE-2026-32283, CVE-2026-32289, CVE-2026-33186, CVE-2026-33810, CVE-2026-33811, CVE-2026-33814, CVE-2026-39817, CVE-2026-39819, CVE-2026-39820, CVE-2026-39821, CVE-2026-39823, CVE-2026-39824, CVE-2026-39825, CVE-2026-39826, CVE-2026-39827, CVE-2026-39828, CVE-2026-39829, CVE-2026-39830, CVE-2026-39831, CVE-2026-39832, CVE-2026-39833, CVE-2026-39834, CVE-2026-39835, CVE-2026-39836, CVE-2026-42499, CVE-2026-42501, CVE-2026-42502, CVE-2026-42506, CVE-2026-42508, CVE-2026-46595, CVE-2026-46597, CVE-2026-46598, ghsa-f6x5-jh6r-wrfv, ghsa-hfvc-g4fc-pqhx, ghsa-j5w8-q4qc-rx2x, ghsa-p77j-4mvh-x3m3 applied in versions: 8.4.0-r0, 8.5.0-r0, 8.5.0-r1, 8.5.0-r2, 8.5.0-r3 | 2026-06-08T12:49:49.195236Z | 2026-06-05T06:06:00Z |
| cleanstart-2026-re02723 | Security fixes for CVE-2025-61726, CVE-2025-61728, CVE-2025-61730, CVE-2025-68121, CVE-2026-24051, CVE-2026-25679, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-27139, CVE-2026-27142, CVE-2026-32281, CVE-2026-32283, CVE-2026-33186, CVE-2026-33810, CVE-2026-33811, CVE-2026-33814, CVE-2026-39817, CVE-2026-39819, CVE-2026-39820, CVE-2026-39821, CVE-2026-39823, CVE-2026-39824, CVE-2026-39825, CVE-2026-39826, CVE-2026-39827, CVE-2026-39828, CVE-2026-39829, CVE-2026-39830, CVE-2026-39831, CVE-2026-39832, CVE-2026-39833, CVE-2026-39834, CVE-2026-39835, CVE-2026-39836, CVE-2026-39883, CVE-2026-42499, CVE-2026-42501, CVE-2026-42502, CVE-2026-42506, CVE-2026-42508, CVE-2026-46595, CVE-2026-46597, CVE-2026-46598, ghsa-9h8m-3fm2-qjrq, ghsa-p77j-4mvh-x3m3 applied in versions: 6.1.0-r0, 6.1.0-r1, 6.1.0-r2, 6.1.0-r3, 6.1.0-r4 | 2026-06-08T12:59:56.014836Z | 2026-06-05T05:57:22Z |
| cleanstart-2026-qn97697 | Security fixes for CVE-2025-14847, CVE-2025-58181, CVE-2025-61727, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-27145, CVE-2026-32280, CVE-2026-32281, CVE-2026-32282, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289, CVE-2026-33814, CVE-2026-39821, CVE-2026-39824, CVE-2026-39827, CVE-2026-39828, CVE-2026-39829, CVE-2026-39830, CVE-2026-39831, CVE-2026-39832, CVE-2026-39833, CVE-2026-39834, CVE-2026-39835, CVE-2026-42502, CVE-2026-42504, CVE-2026-42506, CVE-2026-42507, CVE-2026-42508, CVE-2026-46595, CVE-2026-46597, CVE-2026-46598 applied in versions: 8.2.1-r1, 8.2.5-r0, 8.3.2-r0, 8.3.2-r1 | 2026-06-08T13:02:13.745824Z | 2026-06-05T05:48:38Z |
| cleanstart-2026-qu83011 | Security fixes for CVE-2025-54410, CVE-2026-27145, CVE-2026-32952, CVE-2026-33186, CVE-2026-33811, CVE-2026-33814, CVE-2026-39817, CVE-2026-39819, CVE-2026-39820, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39827, CVE-2026-39828, CVE-2026-39829, CVE-2026-39830, CVE-2026-39831, CVE-2026-39832, CVE-2026-39833, CVE-2026-39834, CVE-2026-39835, CVE-2026-39836, CVE-2026-40179, CVE-2026-42499, CVE-2026-42501, CVE-2026-42504, CVE-2026-42507, CVE-2026-42508, CVE-2026-46595, CVE-2026-46597, CVE-2026-46598, ghsa-4vq8-7jfc-9cvp, ghsa-p77j-4mvh-x3m3, ghsa-pjcq-xvwq-hhpj, ghsa-vffh-x6r8-xx99, ghsa-wg65-39gg-5wfj applied in versions: 8.18.1-r0, 8.19.15-r0, 8.19.15-r2, 8.19.15-r3, 8.19.15-r5, 8.19.15-r6, 9.1.10-r0 | 2026-06-08T13:10:53.763543Z | 2026-06-05T05:45:29Z |
| cleanstart-2026-rl64341 | Security fixes for CVE-2025-61729, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-32952, CVE-2026-39821, CVE-2026-39827, CVE-2026-39828, CVE-2026-39829, CVE-2026-39830, CVE-2026-39831, CVE-2026-39832, CVE-2026-39833, CVE-2026-39834, CVE-2026-39835, CVE-2026-39883, CVE-2026-42502, CVE-2026-42506, CVE-2026-42508, CVE-2026-46595, CVE-2026-46597, CVE-2026-46598, ghsa-hfvc-g4fc-pqhx, ghsa-mh2q-q3fh-2475, ghsa-pjcq-xvwq-hhpj applied in versions: 1.1.0-r0, 2.4.1-r0, 2.5.0-r0, 2.5.0-r1 | 2026-06-08T13:17:34.094120Z | 2026-06-05T04:34:32Z |
| cleanstart-2026-rr82368 | Security fixes for CVE-2025-13151, CVE-2026-22695, CVE-2026-22801, CVE-2026-2332, CVE-2026-24515, CVE-2026-25210, CVE-2026-25646, ghsa-72hv-8253-57qq applied in versions: 3.7.2-r4, 3.7.2-r5, 3.7.2-r6 | 2026-06-08T13:21:05.174938Z | 2026-06-05T04:16:47Z |
| cleanstart-2026-ok95571 | Security fixes for CVE-2025-47911, CVE-2025-47912, CVE-2025-58183, CVE-2025-58186, CVE-2025-58188, CVE-2025-58190, CVE-2025-61723, CVE-2025-61724, CVE-2025-61729, CVE-2026-25679, CVE-2026-27137, CVE-2026-27138, CVE-2026-27139, CVE-2026-27142 applied in versions: 1.4.10-r0, 1.4.13-r0, 1.4.14-r0, 1.4.8-r0 | 2026-06-08T13:46:34.241098Z | 2026-06-04T10:47:04Z |
| cleanstart-2026-ru36468 | Security fixes for CVE-2026-0636, CVE-2026-3260, CVE-2026-33558, CVE-2026-33870, CVE-2026-33871, CVE-2026-3505, CVE-2026-35554, CVE-2026-41417, CVE-2026-42402, CVE-2026-42403, CVE-2026-42404, CVE-2026-42578, CVE-2026-42579, CVE-2026-42580, CVE-2026-42581, CVE-2026-42583, CVE-2026-42584, CVE-2026-42585, CVE-2026-42587, CVE-2026-5588, CVE-2026-5598, ghsa-287c-fxr7-3w6c, ghsa-2hfh-9h53-qc24, ghsa-38f8-5428-x5cv, ghsa-45q3-82m4-75jr, ghsa-57rv-r2g8-2cj3, ghsa-5qcv-4rpc-jp93, ghsa-72hv-8253-57qq, ghsa-c3fc-8qff-9hwx, ghsa-cj8j-37rh-8475, ghsa-cm33-6792-r9fm, ghsa-f6hv-jmp6-3vwv, ghsa-g36m-9g3m-2vmp, ghsa-m4cv-j2px-7723, ghsa-mj4r-2hfc-f8p6, ghsa-p93r-85wp-75v3, ghsa-pwqr-wmgm-9rr8, ghsa-v8h7-rr48-vmmv, ghsa-w9fj-cfpg-grvv, ghsa-wf66-mphr-4c4r, ghsa-wg6q-6289-32hp, ghsa-xxqh-mfjm-7mv9 applied in versions: 39.0.1-r0 | 2026-06-08T14:00:50.454920Z | 2026-06-04T05:30:36Z |
| cleanstart-2026-ph30270 | Security fixes for CVE-2025-47912, CVE-2025-58183, CVE-2025-58185, CVE-2025-58186, CVE-2025-58187, CVE-2025-58188, CVE-2025-58189, CVE-2025-61723, CVE-2025-61724, CVE-2025-61725, CVE-2025-61726, CVE-2025-61727, CVE-2025-61728, CVE-2025-61729, CVE-2025-61730, CVE-2025-61731, CVE-2025-61732, CVE-2025-68119, CVE-2025-68121, CVE-2026-25679, CVE-2026-25680, CVE-2026-27139, CVE-2026-27142, CVE-2026-27145, CVE-2026-33814, CVE-2026-39821, CVE-2026-39833, CVE-2026-39836, CVE-2026-42499, CVE-2026-42504, CVE-2026-42507, CVE-2026-42508, CVE-2026-46595, ghsa-f6x5-jh6r-wrfv, ghsa-j5w8-q4qc-rx2x, ghsa-p436-gjf2-799p applied in versions: 7.1.1-r0, 7.1.1-r1, 7.1.1-r3, 7.1.1-r4, 7.1.1-r5 | 2026-06-08T14:10:29.174191Z | 2026-06-03T12:05:10Z |
| cleanstart-2026-rr97166 | Security fixes for CVE-2021-38561, CVE-2022-27191 applied in versions: 3.1.2-r3, 3.1.2-r4 | 2026-06-08T14:19:27.617592Z | 2026-06-03T10:25:19Z |