NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
50 matching advisories · page 1 of 2Index updated 10 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2026-58374 In hostapd before 2.12, a missing bounds check in AP-mode Wi-Fi 7 (IEEE 802.11be) Multi-Link Operation (MLO) association request processing allows an unauthent… w1.fi · hostapd 2026-06-30 low3.7 CVE-2025-24912 hostapd fails to process crafted RADIUS packets properly. w1.fi · hostapd 2025-03-12 medium6.5 CVE-2022-37660 In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. w1.fi · hostapd 2025-02-11 high8.8 CVE-2024-5290 An issue was discovered in Ubuntu wpa_supplicant that resulted in loading of arbitrary shared objects, which allows a local unprivileged attacker to escalate p… w1.fi · wpa_supplicant 2024-08-07 medium6.5 CVE-2023-52160 The implementation of PEAP in wpa_supplicant through 2.10 allows authentication bypass. debian · debian_linux, fedoraproject · fedora, redhat · enterprise_linux +1 2024-02-22 critical9.8 CVE-2022-23304 The implementations of EAP-pwd in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side-channel attacks as a result of cache access pattern… w1.fi · hostapd, w1.fi · wpa_supplicant, fedoraproject · fedora 2022-01-17 critical9.8 CVE-2022-23303 The implementations of SAE in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side channel attacks as a result of cache access patterns. w1.fi · hostapd, w1.fi · wpa_supplicant, fedoraproject · fedora 2022-01-17 medium5.3 CVE-2021-30004 In wpa_supplicant and hostapd 2.9, forging attacks may occur because AlgorithmIdentifier parameters are mishandled in tls/pkcs1.c and tls/x509v3.c. w1.fi · hostapd, w1.fi · wpa_supplicant 2021-04-02 high7.5 CVE-2021-27803 A vulnerability was discovered in how p2p/p2p_pd.c in wpa_supplicant before 2.10 processes P2P (Wi-Fi Direct) provision discovery requests. w1.fi · wpa_supplicant, fedoraproject · fedora, debian · debian_linux 2021-02-26 high7.5 CVE-2020-12695 The Open Connectivity Foundation UPnP specification before 2020-04-17 does not forbid the acceptance of a subscription request with a delivery URL on a differe… ui · unifi_controller, w1.fi · hostapd, asus · rt-n11 +9 2020-06-08 high7.5 CVE-2019-10064 hostapd before 2.6, in EAP mode, makes calls to the rand() and random() standard library functions without any preceding srand() or srandom() call, which resul… w1.fi · hostapd, debian · debian_linux 2020-02-28 medium6.5 CVE-2019-5062 An exploitable denial-of-service vulnerability exists in the 802.11w security state handling for hostapd 2.6 connected clients with valid 802.11w sessions. w1.fi · hostapd 2019-12-12 medium6.5 CVE-2019-5061 An exploitable denial-of-service vulnerability exists in the hostapd 2.6, where an attacker could trigger AP to send IAPP location updates for stations, before… w1.fi · hostapd 2019-12-12 medium6.5 CVE-2019-16275 hostapd before 2.10 and wpa_supplicant before 2.10 allow an incorrect indication of disconnection in certain situations because source address validation is mi… w1.fi · hostapd, w1.fi · wpa_supplicant, debian · debian_linux +1 2019-09-12 medium5.9 CVE-2019-13377 The implementations of SAE and EAP-pwd in hostapd and wpa_supplicant 2.x through 2.8 are vulnerable to side-channel attacks as a result of observable timing di… w1.fi · hostapd, fedoraproject · fedora, canonical · ubuntu_linux +1 2019-08-15 medium5.9 CVE-2019-11555 The EAP-pwd implementation in hostapd (EAP server) before 2.8 and wpa_supplicant (EAP peer) before 2.8 does not validate fragmentation reassembly state properl… w1.fi · hostapd, w1.fi · wpa_supplicant 2019-04-26 high8.1 CVE-2019-9499 The implementations of EAP-PWD in wpa_supplicant EAP Peer, when built against a crypto library missing explicit validation on imported elements, do not validat… w1.fi · hostapd, w1.fi · wpa_supplicant, fedoraproject · fedora +6 2019-04-17 high8.1 CVE-2019-9498 The implementations of EAP-PWD in hostapd EAP Server, when built against a crypto library missing explicit validation on imported elements, do not validate the… w1.fi · hostapd, w1.fi · wpa_supplicant, fedoraproject · fedora +6 2019-04-17 high8.1 CVE-2019-9497 The implementations of EAP-PWD in hostapd EAP Server and wpa_supplicant EAP Peer do not validate the scalar and element values in EAP-pwd-Commit. w1.fi · hostapd, w1.fi · wpa_supplicant, fedoraproject · fedora 2019-04-17 high7.5 CVE-2019-9496 An invalid authentication sequence could result in the hostapd process terminating due to missing state validation steps when processing the SAE confirm messag… w1.fi · hostapd, w1.fi · wpa_supplicant, fedoraproject · fedora 2019-04-17 low3.7 CVE-2019-9495 The implementations of EAP-PWD in hostapd and wpa_supplicant are vulnerable to side-channel attacks as a result of cache access patterns. w1.fi · hostapd, w1.fi · wpa_supplicant, fedoraproject · fedora +6 2019-04-17 medium5.9 CVE-2019-9494 The implementations of SAE in hostapd and wpa_supplicant are vulnerable to side channel attacks as a result of observable timing differences and cache access p… w1.fi · hostapd, w1.fi · wpa_supplicant, fedoraproject · fedora +5 2019-04-17 high7.5 CVE-2016-10743 hostapd before 2.6 does not prevent use of the low-quality PRNG that is reached by an os_random() function call. w1.fi · hostapd 2019-03-23 medium6.5 CVE-2018-14526 An issue was discovered in rsn_supp/wpa.c in wpa_supplicant 2.0 through 2.6. canonical · ubuntu_linux, debian · debian_linux, w1.fi · wpa_supplicant 2018-08-08 medium5.9 CVE-2015-5316 The eap_pwd_perform_confirm_exchange function in eap_peer/eap_pwd.c in wpa_supplicant 2.x before 2.6, when EAP-pwd is enabled in a network configuration profil… w1.fi · wpa_supplicant, debian · debian_linux 2018-02-21 medium5.9 CVE-2015-5315 The eap_pwd_process function in eap_peer/eap_pwd.c in wpa_supplicant 2.x before 2.6 does not validate that the reassembly buffer is large enough for the final … w1.fi · wpa_supplicant, debian · debian_linux 2018-02-21 medium5.9 CVE-2015-5314 The eap_pwd_process function in eap_server/eap_server_pwd.c in hostapd 2.x before 2.6 does not validate that the reassembly buffer is large enough for the fina… w1.fi · wpa_supplicant, debian · debian_linux 2018-02-21 medium5.3 CVE-2017-13088 Wi-Fi Protected Access (WPA and WPA2) that support 802.11v allows reinstallation of the Integrity Group Temporal Key (IGTK) when processing a Wireless Network … canonical · ubuntu_linux, debian · debian_linux, freebsd · freebsd +9 2017-10-17 medium5.3 CVE-2017-13087 Wi-Fi Protected Access (WPA and WPA2) that support 802.11v allows reinstallation of the Group Temporal Key (GTK) when processing a Wireless Network Management … canonical · ubuntu_linux, debian · debian_linux, freebsd · freebsd +9 2017-10-17 medium6.8 CVE-2017-13086 Wi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Tunneled Direct-Link Setup (TDLS) Peer Key (TPK) during the TDLS handshake, allowing an atta… canonical · ubuntu_linux, debian · debian_linux, freebsd · freebsd +9 2017-10-17

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.