Vulnerabilities
Recent vulnerabilities
Recent vulnerabilities from
π GNA-1 (CIRCL)
Select from 80 available sources using the dropdown above.
Cleanstart is not individually searchable yet β the search will cover the sources available on the search page.
| ID | Description | Published | Updated |
|---|---|---|---|
| cleanstart-2026-lb41442 | Security fixes for CVE-2021-0341, CVE-2022-1471, CVE-2023-3635, CVE-2025-67735, CVE-2026-33870, CVE-2026-33871, CVE-2026-41417, 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-44249, CVE-2026-45416, CVE-2026-45536, CVE-2026-45673, CVE-2026-45674, CVE-2026-47244, CVE-2026-47691, CVE-2026-48043, CVE-2026-50010, CVE-2026-50020, CVE-2026-50560, CVE-2026-54512, CVE-2026-54513, CVE-2026-54514, CVE-2026-54515, ghsa-38f8-5428-x5cv, ghsa-3cqm-mf7h-prrj, ghsa-3qp7-7mw8-wx86, ghsa-45q3-82m4-75jr, ghsa-563q-j3cm-6jxm, ghsa-57rv-r2g8-2cj3, ghsa-5jmj-h7xm-6q6v, ghsa-5pvg-856g-cp85, ghsa-5x3r-wrvg-rp6q, ghsa-676x-f7gg-47vc, ghsa-72hv-8253-57qq, ghsa-84h7-rjj3-6jx4, ghsa-c2gf-v879-257j, ghsa-c653-97m9-rcg9, ghsa-cm33-6792-r9fm, ghsa-f6hv-jmp6-3vwv, ghsa-hgj6-7826-r7m5, ghsa-hvcg-qmg6-jm4c, ghsa-j3rv-43j4-c7qm, ghsa-m4cv-j2px-7723, ghsa-mj4r-2hfc-f8p6, ghsa-mjmj-j48q-9wg2, ghsa-pwqr-wmgm-9rr8, ghsa-rmj7-2vxq-3g9f, ghsa-v8h7-rr48-vmmv, ghsa-w33c-445m-f8w7, ghsa-w573-9ffj-6ff9, ghsa-w9fj-cfpg-grvv, ghsa-x4gw-5cx5-pgmh, ghsa-xmv7-r254-6q78, ghsa-xxqh-mfjm-7mv9 applied in versions: 3.3.0-r1, 3.3.0-r2 | 2026-07-21T06:42:13.345648Z | 2026-07-21T05:11:18Z |
| cleanstart-2026-jv36933 | Security fixes for CVE-2026-46600, CVE-2026-56852 applied in versions: 1.22.1-r0 | 2026-07-21T06:32:14.326992Z | 2026-07-21T05:11:18Z |
| cleanstart-2026-fv79231 | Netty is a network application framework for development of protocol servers and clients | 2026-07-22T00:41:44.549973Z | 2026-07-21T05:11:18Z |
| cleanstart-2026-ep65920 | Parsing an invalid SVCB or HTTPS RR can panic when the size of a parameter value overflows the message buffer | 2026-07-22T00:36:08.939353Z | 2026-07-21T05:11:18Z |
| cleanstart-2026-bf01272 | Parsing an invalid SVCB or HTTPS RR can panic when the size of a parameter value overflows the message buffer | 2026-07-22T00:33:38.378827Z | 2026-07-21T05:11:18Z |
| cleanstart-2026-ac64135 | Security fixes for CVE-2020-11100 applied in versions: 2.1.4-r0 | 2026-07-21T06:31:47.853141Z | 2026-07-21T05:11:18Z |
| cleanstart-2026-za15834 | Security fixes for CVE-2026-39822, CVE-2026-42504, CVE-2026-42505, CVE-2026-56852 applied in versions: 1.11.1-r7 | 2026-07-21T06:33:56.414167Z | 2026-07-20T13:14:08Z |
| cleanstart-2026-ph23874 | Security fixes for CVE-2025-61729, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-32952, CVE-2026-39821, CVE-2026-39822, CVE-2026-39883, CVE-2026-42502, CVE-2026-42505, CVE-2026-42506, CVE-2026-46600, CVE-2026-56852, ghsa-hfvc-g4fc-pqhx, ghsa-mh2q-q3fh-2475, ghsa-mpwr-8vm7-h73f, ghsa-pjcq-xvwq-hhpj applied in versions: 1.1.0-r0, 2.4.1-r0, 2.5.0-r0, 2.6.0-r1, 2.6.0-r3, 2.7.0-r1 | 2026-07-21T06:40:10.067937Z | 2026-07-20T13:11:58Z |
| cleanstart-2026-bk55944 | Security fixes for CVE-2025-59250, CVE-2026-0636, CVE-2026-33870, CVE-2026-33871, CVE-2026-39852, CVE-2026-41417, CVE-2026-42198, CVE-2026-42577, 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-44249, CVE-2026-44893, CVE-2026-45416, CVE-2026-45536, CVE-2026-45673, CVE-2026-45674, CVE-2026-47244, CVE-2026-47691, CVE-2026-48043, CVE-2026-48059, CVE-2026-50010, CVE-2026-50020, CVE-2026-50559, CVE-2026-50560, CVE-2026-54291, CVE-2026-54512, CVE-2026-54513, CVE-2026-54514, CVE-2026-54515, CVE-2026-54516, CVE-2026-54517, CVE-2026-54518, CVE-2026-5588, CVE-2026-5598, CVE-2026-57914, CVE-2026-9563, ghsa-3qp7-7mw8-wx86, ghsa-563q-j3cm-6jxm, ghsa-5pvg-856g-cp85, ghsa-5x3r-wrvg-rp6q, ghsa-676x-f7gg-47vc, ghsa-72hv-8253-57qq, ghsa-98qh-xjc8-98pq, ghsa-c2gf-v879-257j, ghsa-c3fc-8qff-9hwx, ghsa-c653-97m9-rcg9, ghsa-cc37-9q2j-3hfv, ghsa-h2qv-fj59-j46j, ghsa-hvcg-qmg6-jm4c, ghsa-p93r-85wp-75v3, ghsa-pwqr-wmgm-9rr8, ghsa-rc95-pcm8-65v9, ghsa-v8h7-rr48-vmmv, ghsa-w573-9ffj-6ff9, ghsa-w9fj-cfpg-grvv, ghsa-wg6q-6289-32hp, ghsa-x4gw-5cx5-pgmh, ghsa-xmv7-r254-6q78 applied in versions: 26.5.6-r3, 26.6.1-r1, 26.6.3-r2, 26.6.3-r3 | 2026-07-21T06:46:56.955226Z | 2026-07-20T13:11:12Z |
| cleanstart-2026-cr75797 | Security fixes for CVE-2026-25645, CVE-2026-39822, CVE-2026-42505, CVE-2026-59884, CVE-2026-59885, CVE-2026-59886 applied in versions: 2.20.0-r0, 2.20.0-r1 | 2026-07-21T06:43:58.236918Z | 2026-07-20T13:09:50Z |
| cleanstart-2026-mz40522 | Security fixes for CVE-2026-39822, CVE-2026-42504, CVE-2026-42505 applied in versions: 0.22.1-r0, 0.24.6-r2 | 2026-07-21T06:44:49.917345Z | 2026-07-20T11:25:28Z |
| cleanstart-2026-yt82900 | 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-61729, CVE-2026-27139, CVE-2026-27145, CVE-2026-32282, CVE-2026-32288, CVE-2026-32289, CVE-2026-33186, CVE-2026-39817, CVE-2026-39819, CVE-2026-39822, CVE-2026-39823, CVE-2026-39824, CVE-2026-39825, CVE-2026-39826, CVE-2026-42502, CVE-2026-42504, CVE-2026-42505, CVE-2026-42506, CVE-2026-42507, CVE-2026-56852, ghsa-p77j-4mvh-x3m3 applied in versions: 0.7.1-r0, 0.7.1-r1, 0.7.1-r2, 0.7.1-r3, 0.7.1-r4 | 2026-07-21T06:51:03.701832Z | 2026-07-20T11:14:49Z |
| cleanstart-2026-sp73148 | 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-26958, CVE-2026-27136, CVE-2026-27139, CVE-2026-27142, CVE-2026-27145, CVE-2026-32280, CVE-2026-32281, CVE-2026-32282, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289, CVE-2026-33186, CVE-2026-33811, CVE-2026-33814, CVE-2026-33815, CVE-2026-33816, CVE-2026-34986, CVE-2026-39820, CVE-2026-39821, CVE-2026-39822, 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-40890, CVE-2026-41602, CVE-2026-41889, CVE-2026-42499, CVE-2026-42502, CVE-2026-42504, CVE-2026-42505, CVE-2026-42506, CVE-2026-42507, CVE-2026-42508, CVE-2026-46595, CVE-2026-46597, CVE-2026-46598, CVE-2026-5199, CVE-2026-5724 applied in versions: 1.5.1-r0 | 2026-07-21T06:56:15.300835Z | 2026-07-20T11:14:49Z |
| cleanstart-2026-rv11606 | 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-58190, CVE-2025-61723, CVE-2025-61724, CVE-2025-61725, CVE-2025-61729, CVE-2026-25679, CVE-2026-27137, CVE-2026-27138, CVE-2026-27139, CVE-2026-27142, CVE-2026-39822, CVE-2026-42505, CVE-2026-46600, CVE-2026-56852 applied in versions: 1.4.10-r0, 1.4.13-r0, 1.4.14-r0, 1.4.19-r0, 1.4.8-r0 | 2026-07-21T06:52:12.517606Z | 2026-07-20T06:31:46Z |
| cleanstart-2026-hp74907 | Security fixes for CVE-2025-22868, 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-58190, CVE-2025-61723, CVE-2025-61724, CVE-2025-61725, CVE-2025-61729, CVE-2026-25679, CVE-2026-27137, CVE-2026-27138, CVE-2026-27139, CVE-2026-27142, CVE-2026-33811, CVE-2026-33814, CVE-2026-39817, CVE-2026-39819, CVE-2026-39820, CVE-2026-39822, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39836, CVE-2026-42499, CVE-2026-42501, CVE-2026-42505, CVE-2026-56852, ghsa-6v2p-p543-phr9 applied in versions: 1.1.0-r0, 1.1.0-r1, 1.1.0-r2, 1.4.10-r0, 1.4.13-r0, 1.4.14-r0, 1.4.8-r0 | 2026-07-21T06:54:41.067882Z | 2026-07-20T06:30:15Z |
| cleanstart-2026-kb08955 | Security fixes for CVE-2025-61729, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-27140, CVE-2026-27143, CVE-2026-27144, CVE-2026-27145, CVE-2026-32280, CVE-2026-32281, CVE-2026-32282, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289, CVE-2026-33186, CVE-2026-33810, CVE-2026-33811, CVE-2026-33814, CVE-2026-39820, CVE-2026-39821, CVE-2026-39822, 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-42499, CVE-2026-42501, CVE-2026-42502, CVE-2026-42504, CVE-2026-42505, CVE-2026-42506, CVE-2026-42507, CVE-2026-42508, CVE-2026-46595, CVE-2026-46597, CVE-2026-46598, CVE-2026-46600, CVE-2026-56852, ghsa-p77j-4mvh-x3m3 applied in versions: 1.0.1-r0, 1.1.0-r0, 1.1.0-r1, 1.1.2-r2, 1.1.2-r3 | 2026-07-21T07:01:56.332263Z | 2026-07-20T06:11:57Z |
| cleanstart-2026-um67329 | Security fixes for CVE-2025-61729, CVE-2026-27140, 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-33186, CVE-2026-33810, CVE-2026-33811, CVE-2026-33814, CVE-2026-39820, CVE-2026-39822, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39836, CVE-2026-42499, CVE-2026-42501, CVE-2026-42505, CVE-2026-56852, ghsa-p77j-4mvh-x3m3 applied in versions: 0.9.2-r0, 1.0.1-r0, 1.1.0-r0 | 2026-07-21T07:01:33.006587Z | 2026-07-20T06:10:44Z |
| cleanstart-2026-vy16523 | Security fixes for CVE-2026-39822, CVE-2026-42505, CVE-2026-46600, CVE-2026-56852 applied in versions: 0.8.0-r1 | 2026-07-21T07:00:28.882512Z | 2026-07-20T06:02:19Z |
| cleanstart-2026-rt37134 | 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-61729, CVE-2026-25679, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-27137, CVE-2026-27138, 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-39821, CVE-2026-39822, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39836, CVE-2026-42499, CVE-2026-42501, CVE-2026-42502, CVE-2026-42505, CVE-2026-42506, CVE-2026-56852 applied in versions: 0.10.0-r0, 0.10.0-r1, 0.11.0-r0, 0.11.0-r1, 0.11.0-r2, 0.11.0-r3, 1.13.1-r0 | 2026-07-21T07:05:22.722949Z | 2026-07-20T05:47:51Z |
| cleanstart-2026-ld38774 | 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-61729, CVE-2026-25679, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-27137, CVE-2026-27138, 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-39821, CVE-2026-39822, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39836, CVE-2026-42499, CVE-2026-42501, CVE-2026-42502, CVE-2026-42505, CVE-2026-42506, CVE-2026-56852 applied in versions: 0.10.0-r0, 0.10.0-r1, 0.10.0-r3, 0.11.0-r0, 0.11.0-r1, 0.11.0-r2, 1.13.1-r0 | 2026-07-21T07:06:11.112319Z | 2026-07-20T05:45:52Z |
| cleanstart-2026-gr10254 | Security fixes for CVE-2026-0994, CVE-2026-50271 applied in versions: 1.90.2-r1, 1.91.3-r0 | 2026-07-21T07:03:05.053321Z | 2026-07-20T05:28:42Z |
| cleanstart-2026-om32721 | Security fixes for CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-27145, CVE-2026-39821, CVE-2026-39824, CVE-2026-41080, CVE-2026-42502, CVE-2026-42504, CVE-2026-42506, CVE-2026-42507, CVE-2026-45186, CVE-2026-46600, CVE-2026-56852 applied in versions: 1.13.9-r0, 1.14.5-r1, 1.14.5-r2 | 2026-07-21T07:08:50.072207Z | 2026-07-17T13:43:12Z |
| cleanstart-2026-vu72808 | Security fixes for CVE-2025-61729, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-32952, CVE-2026-39821, CVE-2026-39822, CVE-2026-39883, CVE-2026-42502, CVE-2026-42505, CVE-2026-42506, CVE-2026-46600, CVE-2026-56852, ghsa-hfvc-g4fc-pqhx, ghsa-mh2q-q3fh-2475, ghsa-mpwr-8vm7-h73f, ghsa-pjcq-xvwq-hhpj applied in versions: 1.1.0-r0, 2.4.1-r0, 2.5.0-r0, 2.6.0-r1, 2.6.0-r3 | 2026-07-21T07:11:52.868291Z | 2026-07-16T13:05:36Z |
| cleanstart-2026-ln45890 | Security fixes for CVE-2024-55549, CVE-2025-24855, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-27145, CVE-2026-39821, CVE-2026-39824, CVE-2026-41080, CVE-2026-42502, CVE-2026-42504, CVE-2026-42506, CVE-2026-42507, CVE-2026-45186, CVE-2026-46600, CVE-2026-56852 applied in versions: 1.14.5-r1, 1.14.5-r2, 1.14.5-r3 | 2026-07-21T07:12:39.755808Z | 2026-07-16T13:04:24Z |
| cleanstart-2026-gy91527 | Security fixes for CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-39821, CVE-2026-39822, 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-42505, CVE-2026-42506, CVE-2026-42508, CVE-2026-46595, CVE-2026-46597, CVE-2026-46598, CVE-2026-46600, CVE-2026-56852 applied in versions: 0.35.0-r3, 0.35.0-r4, 0.35.0-r5 | 2026-07-21T07:15:01.890894Z | 2026-07-16T12:01:22Z |
| cleanstart-2026-ic13101 | Security fixes for CVE-2025-61729, CVE-2026-25679, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-27137, CVE-2026-27138, CVE-2026-27142, CVE-2026-27145, CVE-2026-39821, CVE-2026-42502, CVE-2026-42504, CVE-2026-42506, CVE-2026-42507 applied in versions: 0.20.2-r1, 0.22.1-r2 | 2026-07-21T07:15:34.483394Z | 2026-07-16T11:53:23Z |
| cleanstart-2026-so86245 | Security fixes for CVE-2025-61729, CVE-2026-25679, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-27137, CVE-2026-27138, CVE-2026-27142, CVE-2026-27145, CVE-2026-39821, CVE-2026-39822, CVE-2026-42502, CVE-2026-42504, CVE-2026-42505, CVE-2026-42506, CVE-2026-42507, CVE-2026-46600, CVE-2026-56852 applied in versions: 0.20.2-r1, 0.22.1-r2, 0.23.0-r0 | 2026-07-21T07:16:37.216775Z | 2026-07-16T11:50:58Z |
| cleanstart-2026-jt42679 | Security fixes for CVE-2025-61729, CVE-2026-25679, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-27137, CVE-2026-27138, CVE-2026-27142, CVE-2026-27145, CVE-2026-39821, CVE-2026-39822, CVE-2026-42502, CVE-2026-42504, CVE-2026-42505, CVE-2026-42506, CVE-2026-42507, CVE-2026-46600, CVE-2026-56852 applied in versions: 0.20.2-r1, 0.22.1-r2, 0.24.0-r0 | 2026-07-21T07:18:10.504204Z | 2026-07-16T11:48:02Z |
| cleanstart-2026-bi19096 | 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-61729, CVE-2026-25680, CVE-2026-25681, CVE-2026-27136, CVE-2026-33811, CVE-2026-33814, CVE-2026-39817, CVE-2026-39819, CVE-2026-39820, CVE-2026-39821, CVE-2026-39822, 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-42505, CVE-2026-42508, CVE-2026-46595, CVE-2026-46597, CVE-2026-46598, CVE-2026-56852 applied in versions: 1.7.0-r0, 1.7.1-r0, 1.7.4-r0, 1.7.5-r0 | 2026-07-21T07:22:41.105960Z | 2026-07-16T11:37:06Z |
| cleanstart-2026-nm02768 | Security fixes for CVE-2024-35195 applied in versions: 2.32.3-r0 | 2026-07-21T07:17:48.587941Z | 2026-07-16T11:34:39Z |