| CVE-2020-7457US | high8.1 | 33.1% (98th) | Exploit | ✗no fix | 2020-07-09 | ≤ FreeBSD 12.1-RELEASE before p7, 11.4-RELEASE before p1, 11.3-RELEASE before p11 |
| CVE-2020-7461US | high7.3 | 4.13% (91st) | Exploit | ✗no fix | 2021-03-26 | ≤ FreeBSD 12.1-RELEASE before p9, 11.4-RELEASE before p3, 11.3-RELEASE before p13 |
| CVE-2020-25578US | medium5.3 | 2.31% (83rd) | Exploit | ✗no fix | 2021-03-26 | ≤ FreeBSD 12.2-RELEASE before p3, 12.1-RELEASE before p13, 11.4-RELEASE before p7 |
| CVE-2021-29627US | high7.8 | 0.75% (55th) | Exploit | ✗no fix | 2021-04-07 | ≤ FreeBSD 12.2-RELEASE before p6 |
| CVE-2019-5599US | high7.5 | 5.08% (92nd) | — | ✗no fix | 2019-07-02 | ≤ FreeBSD 12.0 before 12.0-RELEASE-p6 |
| CVE-2019-5611US | high7.5 | 4.42% (91st) | — | ✗no fix | 2019-08-30 | 3 versions |
| CVE-2019-5610US | high7.5 | 3.81% (90th) | — | ✗no fix | 2019-08-30 | 3 versions |
| CVE-2019-5597US | critical9.1 | 3.66% (90th) | — | ✗no fix | 2019-05-15 | ≤ FreeBSD 11.2 before 11.2-RELEASE-p10 and 12.0 before 12.0-RELEASE-p4 |
| CVE-2019-5598US | high7.5 | 3.34% (89th) | — | ✗no fix | 2019-05-15 | ≤ FreeBSD 11.2 before 11.2-RELEASE-p10 and 12.0 before 12.0-RELEASE-p4 |
| CVE-2020-7454US | critical9.8 | 2.71% (86th) | — | ✗no fix | 2020-05-13 | ≤ FreeBSD 12.1-RELEASE before p5, 11.4-BETA1 before p1, and 11.3-RELEASE before p9 |
| CVE-2020-7450US | critical9.8 | 2.52% (85th) | — | ✗no fix | 2020-02-18 | 5 versions |
| CVE-2019-5608US | critical9.8 | 2.13% (82nd) | — | ✗no fix | 2019-08-30 | 3 versions |
| CVE-2020-7458US | critical9.8 | 1.90% (80th) | — | ✗no fix | 2020-07-09 | ≤ FreeBSD 11.4-RELEASE before p1 |
| CVE-2020-7452US | critical9.1 | 1.83% (79th) | — | ✗no fix | 2020-04-29 | ≤ 12.1-STABLE before r357490, 12.1-RELEASE before 12.1-RELEASE-p3, 11.3-STABLE before r357489, 11.3-RELEASE before 11.3-RELEASE-p7 |
| CVE-2021-29630US | high8.1 | 1.58% (75th) | — | ✗no fix | 2021-08-30 | ≤ FreeBSD 13.0-RELEASE before p4, 12.2-RELEASE before p10, 11.4-RELEASE before p13 |
| CVE-2019-15880US | critical9.8 | 1.54% (75th) | — | ✗no fix | 2020-05-13 | ≤ FreeBSD 12.1-RELEASE before p5 |
| CVE-2020-25583US | critical9.8 | 1.52% (74th) | — | ✗no fix | 2021-03-29 | ≤ FreeBSD 12.2-RELEASE before p1, 12.1-RELEASE before p11, 11.4-RELEASE before p5 |
| CVE-2020-25577US | critical9.8 | 1.50% (74th) | — | ✗no fix | 2021-03-29 | ≤ FreeBSD 12.2-RELEASE before p1, 12.1-RELEASE before p11, 11.4-RELEASE before p5 |
| CVE-2019-5614US | critical9.8 | 1.35% (71st) | — | ✗no fix | 2020-04-29 | ≤ FreeBSD 12.1-STABLE before r356035, 12.1-RELEASE before 12.1-RELEASE-p4, 11.3-STABLE before r356036, 11.3-RELEASE before 11.3-RELEASE-p8 |
| CVE-2019-15874US | critical9.8 | 1.35% (71st) | — | ✗no fix | 2020-04-29 | ≤ FreeBSD 12.1-STABLE before r356035, 12.1-RELEASE before 12.1-RELEASE-p4, 11.3-STABLE before r356036, 11.3-RELEASE before 11.3-RELEASE-p8 |
| CVE-2020-7468US | high8.8 | 1.35% (71st) | — | ✗no fix | 2021-03-26 | ≤ FreeBSD 12.1-RELEASE before p10, 11.4-RELEASE before p4, 11.3-RELEASE before p14 |
| CVE-2019-5609US | high7.5 | 1.29% (70th) | — | ✗no fix | 2019-08-30 | 3 versions |
| CVE-2021-29628US | high7.5OT elevated | 1.25% (69th) | — | ✗no fix | 2021-05-28 | ≤ FreeBSD 13.0-RELEASE before p1, 12.2-RELEASE before p7 |
| CVE-2020-7469US | high7.5 | 1.22% (69th) | — | ✗no fix | 2021-06-04 | ≤ FreeBSD 12.2-RELEASE before p1, 12.1-RELEASE before p11, 11.4-RELEASE before p5 |
| CVE-2020-7451US | medium5.3 | 1.17% (67th) | — | ✗no fix | 2020-04-28 | ≤ 12.1-STABLE before r358739, 12.1-RELEASE before 12.1-RELEASE-p3, 11.3-STABLE before r358740, 11.3-RELEASE before 11.3-RELEASE-p7 |
| CVE-2021-29629US | high7.5 | 1.16% (67th) | — | ✗no fix | 2021-05-28 | ≤ FreeBSD 13.0-RELEASE before p1, 12.2-RELEASE before p7, 11.4-RELEASE before p10 |
| CVE-2020-25579US | medium5.3 | 1.12% (66th) | — | ✗no fix | 2021-03-26 | ≤ FreeBSD 12.2-RELEASE before p3, 12.1-RELEASE before p13, 11.4-RELEASE before p7 |
| CVE-2019-5612US | high7.5 | 0.91% (60th) | — | ✗no fix | 2019-08-30 | 3 versions |
| CVE-2021-29632US | high7.5 | 0.85% (58th) | — | ✗no fix | 2022-01-18 | ≤ FreeBSD 13.0-RELEASE before p6, 12.2-RELEASE before p12 |
| CVE-2020-25581US | high7.5 | 0.78% (56th) | — | ✗no fix | 2021-03-26 | ≤ FreeBSD 12.2-RELEASE before p4, 11.4-RELEASE before p8 |
| CVE-2020-7464US | medium5.3 | 0.76% (55th) | — | ✗no fix | 2021-03-26 | ≤ FreeBSD 12.1-RELEASE before p10, 11.4-RELEASE before p4, 11.3-RELEASE before p14 |
| CVE-2020-25580US | medium5.3 | 0.75% (55th) | — | ✗no fix | 2021-03-26 | ≤ FreeBSD 12.2-RELEASE before p4, 11.4-RELEASE before p8 |
| CVE-2020-25582US | high8.7 | 0.72% (54th) | — | ✗no fix | 2021-03-26 | ≤ FreeBSD 12.2-RELEASE before p4, 11.4-RELEASE before p8 |
| CVE-2020-7460US | high7.0 | 0.69% (53rd) | — | ✗no fix | 2020-08-06 | ≤ FreeBSD 12.1-RELEASE before p8, 11.4-RELEASE before p2, 11.3-RELEASE before p12 |
| CVE-2019-15879US | high7.4 | 0.66% (51st) | — | ✗no fix | 2020-05-13 | ≤ FreeBSD 12.1-RELEASE before p5, and 11.3-RELEASE before p9 |
| CVE-2019-5613US | critical9.8OT elevated | 0.58% (47th) | — | ✗no fix | 2020-02-18 | ≤ 12.0 before 12.0-RELEASE-p13 |
| CVE-2020-7456US | medium6.8 | 0.56% (46th) | — | ✗no fix | 2020-06-09 | ≤ FreeBSD 12.1-RELEASE before p6, 11.3-RELEASE before p10, and 11.4-RC2 before p1 |
| CVE-2020-7455US | medium5.5 | 0.55% (46th) | — | ✗no fix | 2020-05-13 | ≤ FreeBSD 12.1-RELEASE before p5, 11.4-BETA1 before p1, and 11.3-RELEASE before p9 |
| CVE-2020-7459US | medium6.8 | 0.41% (35th) | — | ✗no fix | 2020-08-06 | ≤ FreeBSD 12.1-RELEASE before p8, 11.4-RELEASE before p2, 11.3-RELEASE before p12 |
| CVE-2020-7463US | medium5.5 | 0.40% (34th) | — | ✗no fix | 2021-03-26 | ≤ FreeBSD 12.1-RELEASE before p9, 11.4-RELEASE before p3, 11.3-RELEASE before p13 |
| CVE-2020-7453US | medium6.0 | 0.34% (27th) | — | ✗no fix | 2020-04-29 | ≤ 12.1-STABLE before r359021, 12.1-RELEASE before 12.1-RELEASE-p3, 11.3-STABLE before r359020, 11.3-RELEASE before 11.3-RELEASE-p7 |
| CVE-2021-29626US | medium5.5 | 0.34% (27th) | — | ✗no fix | 2021-04-07 | ≤ FreeBSD 12.2-RELEASE before p6, 11.4-RELEASE before p9 |
| CVE-2019-15878US | high7.8 | 0.33% (26th) | — | ✗no fix | 2020-05-13 | ≤ FreeBSD 11.3-RELEASE before p9 |
| CVE-2019-15875US | low3.3 | 0.29% (21st) | — | ✗no fix | 2020-02-18 | 5 versions |
| CVE-2021-29631US | high7.8 | 0.29% (21st) | — | ✗no fix | 2021-08-30 | ≤ FreeBSD 13.0-RELEASE before p4, 12.2-RELEASE before p10, 11.4-RELEASE before p13 |
| CVE-2019-15876US | medium5.5OT elevated | 0.27% (20th) | — | ✗no fix | 2020-04-28 | ≤ 12.1-STABLE before r356089, 12.1-RELEASE before 12.1-RELEASE-p3, 11.3-STABLE before r356090, 11.3-RELEASE before 11.3-RELEASE-p7 |
| CVE-2020-7467US | high7.6 | 0.27% (19th) | — | ✗no fix | 2021-03-26 | ≤ FreeBSD 12.1-RELEASE before p10, 11.4-RELEASE before p4, 11.3-RELEASE before p14 |
| CVE-2019-15877US | medium5.5OT elevated | 0.24% (16th) | — | ✗no fix | 2020-04-28 | ≤ 12.1-STABLE before r356606, 12.1-RELEASE before 12.1-RELEASE-p3 |
| CVE-2020-7462US | medium5.5 | 0.23% (14th) | — | ✗no fix | 2021-03-26 | ≤ FreeBSD 11.3-RELEASE before p13 |
| CVE-2020-25584US | high7.5 | 0.19% (8th) | — | ✗no fix | 2021-04-07 | ≤ FreeBSD 12.2-RELEASE before p6, 11.4-RELEASE before p9 |