- Products & ServicesProducts & Services
- SolutionsSolutions
- PricingPricing
- CompanyCompany
- ResourcesResources
en
en
Severity across 13 analyzed records
As of 10/04/2026, within CyStack's analyzed data, OpenBSD has 2 security vulnerabilities published in the last 90 days. Of these, 1 is rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of OpenBSD and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-103547 | Exploitation statusNot known exploited | FixYes | Published09/30/2026 | SeverityCritical |
CVE-2026-56101OpenBSD ieee80211_crypto_tkip.c TKIP MIC Countermeasure Logic Inversion DoS | Exploitation statusPublic exploit | FixYes | Published09/08/2026 | SeverityMedium |
CVE-2026-57589 | Exploitation statusNot known exploited | FixYes | Published06/25/2026 | SeverityHigh |
CVE-2026-56099OpenBSD mpls_do_error Kernel Stack Memory Disclosure via MPLS Input | Exploitation statusPublic exploit | FixYes | Published06/18/2026 | SeverityMedium |
CVE-2026-55706 | Exploitation statusPublic exploit | FixYes | Published06/17/2026 | SeverityMedium |
CVE-2026-41285 | Exploitation statusNot known exploited | FixYes | Published04/20/2026 | SeverityMedium |
CVE-2025-30334OpenBSD wg(4) kernel crash | Exploitation statusNot known exploited | FixYes | Published03/20/2025 | SeverityHigh |
CVE-2024-11149OpenBSD vmm GDTR limits | Exploitation statusNot known exploited | FixYes | Published12/06/2024 | SeverityMedium |
CVE-2024-10933OpenBSD readdir directory traversal | Exploitation statusNot known exploited | FixYes | Published12/05/2024 | SeverityMedium |
CVE-2024-11148OpenBSD httpd(8) null dereference | Exploitation statusNot known exploited | FixYes | Published12/05/2024 | SeverityHigh |
CVE-2024-10934OpenBSD NFS double-free vulnerability | Exploitation statusNot known exploited | FixNot confirmed | Published11/15/2024 | SeverityCritical |
CVE-2024-43688 | Exploitation statusPublic exploit | FixNot confirmed | Published08/20/2024 | SeverityHigh |
CVE-2021-35000OpenBSD Kernel Multicast Routing Uninitialized Memory Information Disclosure Vulnerability | Exploitation statusNot known exploited | FixNot confirmed | Published05/07/2024 | SeverityLow |
CVE-2021-34999OpenBSD Kernel Multicast Routing Uninitialized Memory Information Disclosure Vulnerability | Exploitation statusNot known exploited | FixNot confirmed | Published05/07/2024 | SeverityLow |
CVE-2024-29937 | Exploitation statusNot known exploited | FixNot confirmed | Published03/21/2024 | SeverityCritical |
CVE-2023-52558OpenBSD 7.4 and 7.3 m_split() network buffer kernel crash | Exploitation statusNot known exploited | FixYes | Published03/01/2024 | SeverityHigh |
CVE-2023-52557OpenBSD 7.3 invalid l2tp message npppd crash | Exploitation statusNot known exploited | FixYes | Published03/01/2024 | SeverityHigh |
CVE-2023-52556OpenBSD 7.4 pf state race condition kernel crash | Exploitation statusNot known exploited | FixYes | Published03/01/2024 | SeverityMedium |
CVE-2023-40216 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2023 | SeverityUnknown |
CVE-2023-35784 | Exploitation statusNot known exploited | FixNot confirmed | Published06/16/2023 | SeverityUnknown |
CVE-2021-46880 | Exploitation statusNot known exploited | FixNot confirmed | Published04/14/2023 | SeverityCritical |
CVE-2022-48437 | Exploitation statusNot known exploited | FixNot confirmed | Published04/12/2023 | SeverityMedium |
CVE-2023-29323 | Exploitation statusNot known exploited | FixNot confirmed | Published04/04/2023 | SeverityUnknown |
CVE-2023-27567 | Exploitation statusNot known exploited | FixNot confirmed | Published03/03/2023 | SeverityUnknown |
CVE-2022-27882 | Exploitation statusNot confirmed | FixNot confirmed | Published03/25/2022 | SeverityUnknown |
CVE-2022-27881 | Exploitation statusNot confirmed | FixNot confirmed | Published03/25/2022 | SeverityUnknown |
CVE-2010-4816 | Exploitation statusNot confirmed | FixNot confirmed | Published06/22/2021 | SeverityUnknown |
CVE-2020-26142 | Exploitation statusNot confirmed | FixNot confirmed | Published05/11/2021 | SeverityUnknown |
CVE-2020-16088 | Exploitation statusNot confirmed | FixNot confirmed | Published07/28/2020 | SeverityUnknown |
CVE-2011-3336 | Exploitation statusNot confirmed | FixNot confirmed | Published02/12/2020 | SeverityUnknown |
CVE-2019-19726 | Exploitation statusNot confirmed | FixNot confirmed | Published12/12/2019 | SeverityUnknown |
CVE-2019-14899 | Exploitation statusNot confirmed | FixNot confirmed | Published12/11/2019 | SeverityHigh |
CVE-2012-1577 | Exploitation statusNot confirmed | FixNot confirmed | Published12/10/2019 | SeverityUnknown |
CVE-2019-19519 | Exploitation statusNot confirmed | FixNot confirmed | Published12/04/2019 | SeverityUnknown |
CVE-2019-19520 | Exploitation statusNot confirmed | FixNot confirmed | Published12/04/2019 | SeverityUnknown |
CVE-2019-19521 | Exploitation statusNot confirmed | FixNot confirmed | Published12/04/2019 | SeverityUnknown |
CVE-2019-19522 | Exploitation statusNot confirmed | FixNot confirmed | Published12/04/2019 | SeverityUnknown |
CVE-2019-8460 | Exploitation statusNot confirmed | FixNot confirmed | Published08/26/2019 | SeverityUnknown |
CVE-2018-14775 | Exploitation statusNot confirmed | FixNot confirmed | Published08/01/2018 | SeverityUnknown |
CVE-2017-1000373 | Exploitation statusPublic exploit | FixNot confirmed | Published06/19/2017 | SeverityUnknown |
CVE-2017-1000372 | Exploitation statusNot confirmed | FixNot confirmed | Published06/19/2017 | SeverityUnknown |
CVE-2017-5850 | Exploitation statusPublic exploit | FixNot confirmed | Published03/27/2017 | SeverityUnknown |
CVE-2016-6350 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2017 | SeverityUnknown |
CVE-2016-6241 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2017 | SeverityUnknown |
CVE-2016-6239 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2017 | SeverityUnknown |
CVE-2016-6247 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2017 | SeverityUnknown |
CVE-2016-6246 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2017 | SeverityUnknown |
CVE-2016-6242 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2017 | SeverityUnknown |
CVE-2016-6522 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2017 | SeverityUnknown |
CVE-2016-6245 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2017 | SeverityUnknown |
CVE-2016-6240 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2017 | SeverityUnknown |
CVE-2016-6243 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2017 | SeverityUnknown |
CVE-2016-6244 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2017 | SeverityUnknown |
CVE-2014-7250 | Exploitation statusNot confirmed | FixNot confirmed | Published12/12/2014 | SeverityUnknown |
CVE-2011-2895 | Exploitation statusNot confirmed | FixNot confirmed | Published08/19/2011 | SeverityUnknown |
CVE-2011-2168 | Exploitation statusNot confirmed | FixNot confirmed | Published05/24/2011 | SeverityUnknown |
CVE-2011-0419 | Exploitation statusNot confirmed | FixNot confirmed | Published05/16/2011 | SeverityUnknown |
CVE-2011-1013 | Exploitation statusNot confirmed | FixNot confirmed | Published05/09/2011 | SeverityUnknown |
CVE-2010-4755 | Exploitation statusNot confirmed | FixNot confirmed | Published03/02/2011 | SeverityUnknown |
CVE-2010-4754 | Exploitation statusNot confirmed | FixNot confirmed | Published03/02/2011 | SeverityUnknown |
CVE-2009-3572 | Exploitation statusNot confirmed | FixNot confirmed | Published10/06/2009 | SeverityUnknown |
CVE-2009-0687 | Exploitation statusPublic exploit | FixNot confirmed | Published08/11/2009 | SeverityUnknown |
CVE-2009-0689 | Exploitation statusNot confirmed | FixNot confirmed | Published07/01/2009 | SeverityUnknown |
CVE-2009-0537 | Exploitation statusPublic exploit | FixNot confirmed | Published03/09/2009 | SeverityUnknown |
CVE-2009-0780 | Exploitation statusNot confirmed | FixNot confirmed | Published03/04/2009 | SeverityUnknown |
CVE-2008-4609 | Exploitation statusNot confirmed | FixNot confirmed | Published10/20/2008 | SeverityUnknown |
CVE-2008-2476 | Exploitation statusNot confirmed | FixNot confirmed | Published10/03/2008 | SeverityUnknown |
CVE-2008-4247 | Exploitation statusNot confirmed | FixNot confirmed | Published09/25/2008 | SeverityUnknown |
CVE-2008-1215 | Exploitation statusNot confirmed | FixNot confirmed | Published03/09/2008 | SeverityUnknown |
CVE-2008-1057 | Exploitation statusNot confirmed | FixNot confirmed | Published02/28/2008 | SeverityUnknown |
CVE-2008-1058 | Exploitation statusNot confirmed | FixNot confirmed | Published02/28/2008 | SeverityUnknown |
CVE-2007-6700 | Exploitation statusNot confirmed | FixNot confirmed | Published02/05/2008 | SeverityUnknown |
CVE-2008-0384 | Exploitation statusPublic exploit | FixNot confirmed | Published01/22/2008 | SeverityUnknown |
CVE-2002-2280 | Exploitation statusNot confirmed | FixNot confirmed | Published10/18/2007 | SeverityUnknown |
CVE-2003-1366 | Exploitation statusNot confirmed | FixNot confirmed | Published10/17/2007 | SeverityUnknown |
CVE-2007-5365 | Exploitation statusPublic exploit | FixNot confirmed | Published10/11/2007 | SeverityUnknown |
CVE-2007-1351 | Exploitation statusNot confirmed | FixNot confirmed | Published04/06/2007 | SeverityUnknown |
CVE-2007-1352 | Exploitation statusNot confirmed | FixNot confirmed | Published04/06/2007 | SeverityUnknown |
CVE-2007-1365 | Exploitation statusNot confirmed | FixNot confirmed | Published03/10/2007 | SeverityUnknown |
CVE-2002-2222 | Exploitation statusNot confirmed | FixNot confirmed | Published02/27/2007 | SeverityUnknown |
CVE-2007-0343 | Exploitation statusNot confirmed | FixNot confirmed | Published01/18/2007 | SeverityUnknown |
CVE-2007-0085 | Exploitation statusNot confirmed | FixNot confirmed | Published01/05/2007 | SeverityUnknown |
CVE-2006-6730 | Exploitation statusNot confirmed | FixNot confirmed | Published12/26/2006 | SeverityUnknown |
CVE-2006-6397 | Exploitation statusNot confirmed | FixNot confirmed | Published12/08/2006 | SeverityUnknown |
CVE-2006-6164 | Exploitation statusNot confirmed | FixNot confirmed | Published11/29/2006 | SeverityUnknown |
CVE-2006-5550 | Exploitation statusNot confirmed | FixNot confirmed | Published10/26/2006 | SeverityUnknown |
CVE-2006-5218 | Exploitation statusNot confirmed | FixNot confirmed | Published10/09/2006 | SeverityUnknown |
CVE-2006-4435 | Exploitation statusNot confirmed | FixNot confirmed | Published08/29/2006 | SeverityUnknown |
CVE-2006-4436 | Exploitation statusNot confirmed | FixNot confirmed | Published08/29/2006 | SeverityUnknown |
CVE-2006-4304 | Exploitation statusNot confirmed | FixNot confirmed | Published08/24/2006 | SeverityUnknown |
CVE-2005-4351 | Exploitation statusNot confirmed | FixNot confirmed | Published01/09/2006 | SeverityUnknown |
CVE-2006-0098 | Exploitation statusNot confirmed | FixNot confirmed | Published01/06/2006 | SeverityUnknown |
CVE-2002-2188 | Exploitation statusNot confirmed | FixNot confirmed | Published11/16/2005 | SeverityUnknown |
CVE-2002-2180 | Exploitation statusNot confirmed | FixNot confirmed | Published11/16/2005 | SeverityUnknown |
CVE-2004-2338 | Exploitation statusNot confirmed | FixNot confirmed | Published08/16/2005 | SeverityUnknown |
CVE-2002-2092 | Exploitation statusNot confirmed | FixNot confirmed | Published08/05/2005 | SeverityUnknown |
CVE-2004-2230 | Exploitation statusNot confirmed | FixNot confirmed | Published07/17/2005 | SeverityUnknown |
CVE-2001-1559 | Exploitation statusNot confirmed | FixNot confirmed | Published07/14/2005 | SeverityUnknown |
CVE-2004-2163 | Exploitation statusNot confirmed | FixNot confirmed | Published07/10/2005 | SeverityUnknown |
CVE-2002-1915 | Exploitation statusNot confirmed | FixNot confirmed | Published06/28/2005 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan