NetSight

Security Dashboard

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

Reset
58 matching advisories · page 2 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.1 CVE-2026-5446 In wolfSSL, ARIA-GCM cipher suites used in TLS 1.2 and DTLS 1.2 reuse an identical 12-byte GCM nonce for every application-data record. wolfssl · wolfssl 2026-04-09 high7.5 CVE-2026-3547 Out-of-bounds read in ALPN parsing due to incomplete validation. wolfssl · wolfssl 2026-03-19 high8.1 CVE-2026-2646 A heap-buffer-overflow vulnerability exists in wolfSSL's wolfSSL_d2i_SSL_SESSION() function. wolfssl · wolfssl 2026-03-19 high7.5 CVE-2026-2645 In wolfSSL 5.8.2 and earlier, a logic flaw existed in the TLS 1.2 server state machine implementation. wolfssl · wolfssl 2026-03-19 high7.1 CVE-2026-0819 A stack buffer overflow vulnerability exists in wolfSSL's PKCS7 SignedData encoding functionality. wolfssl · wolfssl 2026-03-19 high7.5 CVE-2025-12888 Vulnerability in X25519 constant-time cryptographic implementations due to timing side channels introduced by compiler optimizations and CPU architecture limit… wolfssl · wolfssl 2025-11-21 high8.2 CVE-2025-11931 Integer Underflow Leads to Out-of-Bounds Access in XChaCha20-Poly1305 Decrypt. wolfssl · wolfssl 2025-11-21 high7.5 CVE-2025-11935 With TLS 1.3 pre-shared key (PSK) a malicious or faulty server could ignore the request for PFS (perfect forward secrecy) and the client would continue on with… wolfssl · wolfssl 2025-11-21 high7.5 CVE-2024-5991 In function MatchDomainName(), input param str is treated as a NULL terminated string despite being user provided and unchecked. wolfssl · wolfssl 2024-08-27 high7.5 CVE-2024-0901 Remotely executed SEGV and out of bounds read allows malicious packet sender to crash or cause an out of bounds read via sending a malformed packet with the co… wolfssl · wolfssl 2024-03-25 high7.5 CVE-2022-39173 In wolfSSL before 5.5.1, malicious clients can cause a buffer overflow during a TLS 1.3 handshake. wolfssl · wolfssl 2022-09-29 high7.5 CVE-2022-38152 An issue was discovered in wolfSSL before 5.5.0. wolfssl · wolfssl 2022-08-31 high7.5 CVE-2022-34293 wolfSSL before 5.4.0 allows remote attackers to cause a denial of service via DTLS because a check for return-routability can be skipped. wolfssl · wolfssl 2022-08-08 high7.5 CVE-2022-25640 In wolfSSL before 5.2.0, a TLS 1.3 server cannot properly enforce a requirement for mutual authentication. wolfssl · wolfssl 2022-02-24 high8.1 CVE-2021-3336 DoTls13CertificateVerify in tls13.c in wolfSSL before 4.7.0 does not cease processing for certain anomalous peer behavior (sending an ED22519, ED448, ECC, or R… wolfssl · wolfssl 2021-01-29 high7.0 CVE-2020-15309 An issue was discovered in wolfSSL before 4.5.0, when single precision is not employed. wolfssl · wolfssl 2020-08-21 high7.5 CVE-2020-12457 An issue was discovered in wolfSSL before 4.5.0. wolfssl · wolfssl 2020-08-21 high7.5 CVE-2020-11713 wolfSSL 4.3.0 has mulmod code in wc_ecc_mulmod_ex in ecc.c that does not properly resist timing side-channel attacks. wolfssl · wolfssl 2020-04-12 high7.5 CVE-2019-19962 wolfSSL before 4.3.0 mishandles calls to wc_SignatureGenerateHash, leading to fault injection in RSA cryptography. wolfssl · wolfssl 2019-12-25 high7.5 CVE-2014-2904 wolfssl before 3.2.0 has a server certificate that is not properly authorized for server authentication. wolfssl · wolfssl 2019-11-21 high7.5 CVE-2014-2902 wolfssl before 3.2.0 does not properly authorize CA certificate for signing other certificates. wolfssl · wolfssl 2019-11-21 high7.5 CVE-2014-2901 wolfssl before 3.2.0 does not properly issue certificates for a server's hostname. wolfssl · wolfssl 2019-11-21 high7.5 CVE-2019-18840 In wolfSSL 4.1.0 through 4.2.0c, there are missing sanity checks of memory accesses in parsing ASN.1 certificate data while handshaking. wolfssl · wolfssl 2019-11-09 high7.5 CVE-2017-13099 wolfSSL prior to version 3.12.2 provides a weak Bleichenbacher oracle when any TLS cipher suite using RSA key exchange is negotiated. wolfssl · wolfssl, siemens · scalance_w1750d_firmware, arubanetworks · instant 2017-12-13 high7.5 CVE-2017-8855 wolfSSL before 3.11.0 does not prevent wc_DhAgree from accepting a malformed DH key. wolfssl · wolfssl 2017-05-09 high7.8 CVE-2017-8854 wolfSSL before 3.10.2 has an out-of-bounds memory access with loading crafted DH parameters, aka a buffer overflow triggered by a malformed temporary DH file. wolfssl · wolfssl 2017-05-09 high7.5 CVE-2015-6925 wolfSSL (formerly CyaSSL) before 3.6.8 allows remote attackers to cause a denial of service (resource consumption or traffic amplification) via a crafted DTLS … wolfssl · wolfssl 2016-01-22 high7.5 CVE-2009-4484 Multiple stack-based buffer overflows in the CertDecoder::GetName function in src/asn.cpp in TaoCrypt in yaSSL before 1.9.9, as used in mysqld in MySQL 5.0.x b… oracle · mysql, wolfssl · yassl, canonical · ubuntu_linux +2 2009-12-30

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.