| CVE-2017-1084US | high7.5 | 15.3% (97th) | Exploit | ✗no fix | 2018-09-12 | ≤ before 11.2-RELEASE |
| CVE-2025-14558US | — | 6.52% (94th) | Exploit | ✓p8 | 2026-03-09 | 3 versions |
| CVE-2019-5602US | high8.8OT high | 4.01% (91st) | Exploit | ✗no fix | 2019-07-03 | ≤ FreeBSD 12.0 before 12.0-RELEASE-p7 and 11.2 before 11.2-RELEASE-p11 |
| CVE-2026-4747US | — | 3.43% (89th) | Exploit | ✓p1 | 2026-03-26 | 4 versions |
| CVE-2022-23093US | — | 2.40% (84th) | Exploit | ✓p10 | 2024-02-15 | 3 versions |
| CVE-2017-1085US | high7.8 | 1.85% (79th) | Exploit | ✗no fix | 2018-09-12 | ≤ before 11.2-RELEASE |
| CVE-2019-5596US | high8.8 | 1.23% (69th) | Exploit | ✗no fix | 2019-02-12 | ≤ FreeBSD 12.0 before 12.0-RELEASE-p3 |
| CVE-2019-5603US | high7.8 | 0.62% (50th) | Exploit | ✗no fix | 2019-07-26 | 3 versions |
| CVE-2026-45250US | — | 0.41% (35th) | Exploit | ✓p9 | 2026-05-21 | 3 versions |
| CVE-2026-7270US | — | 0.18% (7th) | Exploit | ✓p12 | 2026-04-30 | 4 versions |
| CVE-2026-45258US | — | 0.15% (4th) | Exploit | ✓p15 | 2026-06-27 | 3 versions |
| CVE-2026-49413US | — | 0.13% (2nd) | Exploit | ✓p15 | 2026-06-27 | 3 versions |
| CVE-2026-49417US | — | 0.13% (2nd) | Exploit | ✓p15 | 2026-06-27 | 3 versions |
| CVE-2018-17157US | critical9.8 | 24.2% (98th) | — | ✗no fix | 2018-12-04 | ≤ FreeBSD 11.2 before 11.2-RELEASE-p5 |
| CVE-2019-5600US | critical9.8 | 4.86% (92nd) | — | ✗no fix | 2019-07-03 | ≤ FreeBSD 12.0 before 12.0-RELEASE-p7 and 11.2 before 11.2-RELEASE-p11 |
| CVE-2018-17158US | high7.5 | 4.41% (91st) | — | ✗no fix | 2018-12-04 | ≤ FreeBSD 11.2 before 11.2-RELEASE-p5 |
| CVE-2018-6918US | high7.5 | 4.21% (91st) | — | ✗no fix | 2018-04-04 | ≤ All supported versions of FreeBSD. |
| CVE-2018-17159US | high7.5 | 4.21% (91st) | — | ✗no fix | 2018-12-04 | ≤ FreeBSD 11.2 before 11.2-RELEASE-p5 |
| CVE-2018-6923US | high7.5 | 4.01% (90th) | — | ✗no fix | 2018-09-04 | ≤ All supported versions of FreeBSD. |
| CVE-2022-23088US | — | 3.62% (89th) | — | ✓p1 | 2024-02-15 | 3 versions |
| CVE-2018-17161US | critical9.8 | 3.52% (89th) | — | ✗no fix | 2019-01-03 | ≤ FreeBSD 11.2 before 11.2-RELEASE-p7 and 12.0 before 12.0-RELEASE-p1 |
| CVE-2018-17160US | critical10.0 | 3.35% (89th) | — | ✗no fix | 2018-12-04 | ≤ FreeBSD 11.2 before 11.2-RELEASE-p6 |
| CVE-2018-6922US | medium5.3 | 3.19% (88th) | — | ✗no fix | 2018-08-09 | ≤ All versions prior to 11.2-RELEASE-p1, 11.1-RELEASE-p12, 10.4-RELEASE-p10 |
| CVE-2019-5604US | critical9.6 | 3.09% (88th) | — | ✗no fix | 2019-07-26 | 3 versions |
| CVE-2017-1081US | high7.5 | 2.71% (86th) | — | ✗no fix | 2018-04-10 | ≤ prior to 11.0-RELEASE-p10 and 10.3-RELEASE-p19 |
| CVE-2019-5605US | medium6.5 | 2.33% (83rd) | — | ✗no fix | 2019-07-26 | 3 versions |
| CVE-2018-6916US | critical9.8 | 2.09% (81st) | — | ✗no fix | 2018-03-09 | ≤ All supported versions of FreeBSD |
| CVE-2024-7589US | high8.1 | 2.04% (81st) | — | ✓p9 | 2024-08-12 | 3 versions |
| CVE-2018-6917US | high7.5 | 1.96% (80th) | — | ✗no fix | 2018-04-04 | ≤ All supported versions of FreeBSD. |
| CVE-2018-17156US | medium5.9 | 1.63% (76th) | — | ✗no fix | 2018-11-28 | ≤ FreeBSD 11.2 before 11.2-RELEASE-p5 |
| CVE-2019-5601US | medium6.5 | 1.54% (75th) | — | ✗no fix | 2019-07-03 | ≤ FreeBSD 12.0 before 12.0-RELEASE-p7 and 11.2 before 11.2-RELEASE-p11 |
| CVE-2026-42512US | — | 1.42% (73rd) | — | ✓p13 | 2026-04-30 | 4 versions |
| CVE-2018-6919US | high7.5 | 1.36% (72nd) | — | ✗no fix | 2018-04-04 | ≤ All supported versions of FreeBSD. |
| CVE-2025-14769US | — | 1.17% (67th) | — | ✓p7 | 2026-03-09 | 2 versions |
| CVE-2017-1082US | high7.5 | 1.16% (67th) | — | ✗no fix | 2018-09-12 | ≤ 11.x before 11.1-RELEASE, 10.x before 10.4-RELEASE |
| CVE-2017-1083US | high7.5 | 1.14% (66th) | — | ✗no fix | 2018-09-12 | ≤ before 11.2-RELEASE |
| CVE-2026-4247US | — | 1.14% (66th) | — | ✓p5 | 2026-03-26 | 3 versions |
| CVE-2023-3326US | critical9.8 | 1.10% (65th) | — | ✓13.2-RELEASE-p1 | 2023-06-22 | 3 versions |
| CVE-2023-5941US | critical9.8 | 1.07% (65th) | — | ✓p5 | 2023-11-08 | 2 versions |
| CVE-2023-4809US | high7.5 | 0.80% (56th) | — | ✓p5 | 2023-09-06 | 2 versions |
| CVE-2024-41721US | — | 0.78% (56th) | — | ✓p5 | 2024-09-20 | 4 versions |
| CVE-2023-6534US | high7.5 | 0.74% (54th) | — | ✓p7 | 2023-12-13 | 3 versions |
| CVE-2024-6760US | high7.5OT elevated | 0.74% (54th) | — | ✓p9 | 2024-08-12 | 3 versions |
| CVE-2024-43102US | critical10.0 | 0.68% (52nd) | — | ✓p10 | 2024-09-05 | 3 versions |
| CVE-2024-6759US | medium5.3 | 0.68% (52nd) | — | ✓p5 | 2024-08-12 | 3 versions |
| CVE-2023-5368US | medium6.5OT elevated | 0.67% (52nd) | — | ✓p4 | 2023-10-04 | 2 versions |
| CVE-2022-23092US | — | 0.65% (51st) | — | ✓p12 | 2024-02-15 | 2 versions |
| CVE-2023-3107US | high7.5 | 0.65% (51st) | — | ✓13.2-RELEASE-p2 | 2023-08-01 | 3 versions |
| CVE-2023-0751US | medium6.5 | 0.64% (50th) | — | ✓12.4-RELEASE-p1 | 2023-02-08 | 3 versions |
| CVE-2023-6660US | medium6.5 | 0.62% (50th) | — | ✓p3 | 2023-12-13 | 2 versions |