| CVE-2005-3660: Fix unknown |
| CVE-2007-3719: Fix unknown |
| CVE-2008-2544: Fix unknown |
| CVE-2008-4609: Fix unknown |
| CVE-2010-4563: Fix unknown |
| CVE-2010-5321: Fix unknown |
| CVE-2011-4916: Fix unknown |
| CVE-2011-4917: Fix unknown |
| CVE-2012-4542: Fix unknown |
| CVE-2013-7445: Fix unknown |
| CVE-2015-2877: Fix unknown |
| CVE-2016-8660: Fix unknown |
| CVE-2017-13693: Fix unknown |
| CVE-2017-13694: Fix unknown |
| CVE-2018-1121: Fix unknown |
| CVE-2018-12928: Fix unknown |
| CVE-2018-12929: Fix unknown |
| CVE-2018-12930: Fix unknown |
| CVE-2018-12931: Fix unknown |
| CVE-2018-17977: Fix unknown |
| CVE-2019-12456: Fix unknown |
| CVE-2019-15239: Fix not seen in stream |
| CVE-2019-15290: Fix unknown |
| CVE-2019-15902: Fix not seen in stream |
| CVE-2019-16089: Fix unknown |
| CVE-2019-19378: Fix unknown |
| CVE-2019-19814: Fix unknown |
| CVE-2019-20794: Fix unknown |
| CVE-2020-0347: Fix unknown |
| CVE-2020-10708: Fix unknown |
| CVE-2020-11725: Fix unknown |
| CVE-2020-14304: Fix unknown |
| CVE-2020-15802: Fix unknown |
| CVE-2020-24502: Fix unknown |
| CVE-2020-24503: Fix unknown |
| CVE-2020-25220: Fix not seen in stream |
| CVE-2020-26140: Fix unknown |
| CVE-2020-26142: Fix unknown |
| CVE-2020-26143: Fix unknown |
| CVE-2020-26556: Fix unknown |
| CVE-2020-26557: Fix unknown |
| CVE-2020-26559: Fix unknown |
| CVE-2020-26560: Fix unknown |
| CVE-2020-35501: Fix unknown |
| CVE-2020-36516: Fix unknown |
| CVE-2021-0399: Fix unknown |
| CVE-2021-0695: Fix unknown |
| CVE-2021-26934: Fix unknown |
| CVE-2021-3542: Fix unknown |
| CVE-2021-3714: Fix unknown |
| CVE-2021-3847: Fix unknown |
| CVE-2021-3864: Fix unknown |
| CVE-2021-3892: Fix unknown |
| CVE-2021-39800: Fix unknown |
| CVE-2021-39801: Fix unknown |
| CVE-2021-39802: Fix unknown |
| CVE-2022-0400: Fix unknown |
| CVE-2022-1116: Fix unknown |
| CVE-2022-1247: Fix unknown |
| CVE-2022-1679: Fixed with 5.19.2 |
| CVE-2022-20421: Fixed with 5.19.8 |
| CVE-2022-20422: Fixed with 5.19.2 |
| CVE-2022-2209: Fix unknown |
| CVE-2022-2308: Fixed with 5.19.14 |
| CVE-2022-23825: Fix unknown |
| CVE-2022-25265: Fix unknown |
| CVE-2022-2585: Fixed with 5.19.2 |
| CVE-2022-2586: Fixed with 5.19.2 |
| CVE-2022-2588: Fixed with 5.19.2 |
| CVE-2022-2590: Fixed with 5.19.6 |
| CVE-2022-2602: Fix not seen in stream |
| CVE-2022-26373: Fixed with 5.19.1 |
| CVE-2022-2663: Fixed with 5.19.9 |
| CVE-2022-26878: Fix unknown |
| CVE-2022-2785: Fixed with 5.19.4 |
| CVE-2022-2905: Fixed with 5.19.6 |
| CVE-2022-2961: Fix unknown |
| CVE-2022-2978: Fix not seen in stream |
| CVE-2022-3028: Fixed with 5.19.6 |
| CVE-2022-3169: Fix not seen in stream |
| CVE-2022-3238: Fix unknown |
| CVE-2022-3303: Fixed with 5.19.9 |
| CVE-2022-3344: Fix unknown |
| CVE-2022-3424: Fix unknown |
| CVE-2022-3435: Fix not seen in stream |
| CVE-2022-3521: Fix not seen in stream |
| CVE-2022-3522: Fix not seen in stream |
| CVE-2022-3523: Fix not seen in stream |
| CVE-2022-3524: Fix not seen in stream |
| CVE-2022-3531: Fix unknown |
| CVE-2022-3535: Fix not seen in stream |
| CVE-2022-3541: Fix not seen in stream |
| CVE-2022-3542: Fixed with 5.19.17 |
| CVE-2022-3543: Fix not seen in stream |
| CVE-2022-3544: Fix unknown |
| CVE-2022-3545: Fix not seen in stream |
| CVE-2022-3564: Fix not seen in stream |
| CVE-2022-3565: Fix not seen in stream |
| CVE-2022-3566: Fix not seen in stream |
| CVE-2022-3567: Fix not seen in stream |
| CVE-2022-3586: Fixed with 5.19.9 |
| CVE-2022-3594: Fix not seen in stream |
| CVE-2022-3595: Fix not seen in stream |
| CVE-2022-3619: Fix not seen in stream |
| CVE-2022-3621: Fix not seen in stream |
| CVE-2022-3623: Fix not seen in stream |
| CVE-2022-3624: Fix not seen in stream |
| CVE-2022-3625: Fix not seen in stream |
| CVE-2022-3628: Fix not seen in stream |
| CVE-2022-36280: Fix unknown |
| CVE-2022-3629: Fix not seen in stream |
| CVE-2022-3630: Fix not seen in stream |
| CVE-2022-3633: Fix not seen in stream |
| CVE-2022-3635: Fixed with 5.19.4 |
| CVE-2022-3640: Fix not seen in stream |
| CVE-2022-36402: Fix unknown |
| CVE-2022-3642: Fix unknown |
| CVE-2022-3646: Fix not seen in stream |
| CVE-2022-3649: Fix not seen in stream |
| CVE-2022-36946: Fixed with 5.19 |
| CVE-2022-3707: Fix unknown |
| CVE-2022-38096: Fix unknown |
| CVE-2022-38457: Fix unknown |
| CVE-2022-3903: Fix not seen in stream |
| CVE-2022-39190: Fixed with 5.19.6 |
| CVE-2022-3977: Fix not seen in stream |
| CVE-2022-40133: Fix unknown |
| CVE-2022-40307: Fixed with 5.19.9 |
| CVE-2022-40768: Fixed with 5.19.16 |
| CVE-2022-41218: Fix unknown |
| CVE-2022-41674: Fixed with 5.19.16 |
| CVE-2022-41848: Fix unknown |
| CVE-2022-41849: Fix not seen in stream |
| CVE-2022-41850: Fix not seen in stream |
| CVE-2022-42703: Fixed with 5.19.7 |
| CVE-2022-42719: Fixed with 5.19.16 |
| CVE-2022-42720: Fixed with 5.19.16 |
| CVE-2022-42721: Fixed with 5.19.16 |
| CVE-2022-42722: Fixed with 5.19.16 |
| CVE-2022-42895: Fix not seen in stream |
| CVE-2022-42896: Fix not seen in stream |
| CVE-2022-43750: Fix not seen in stream |
| CVE-2022-43945: Fixed with 5.19.17 |
| CVE-2022-44032: Fix unknown |
| CVE-2022-44033: Fix unknown |
| CVE-2022-44034: Fix unknown |