NetSight

Security Dashboard

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

Reset
661 matching advisories · page 7 of 23Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-28386 Issue summary: Applications using AES-CFB128 encryption or decryption on systems with AVX-512 and VAES support can trigger an out-of-bounds read of up to 15 by… openssl · openssl 2026-04-07 medium6.6 GHSA-c65f-x25w-62jv openssl-encrypt has CORS wildcard with allow_credentials=True in standalone servers pip · openssl-encrypt 2026-04-01 medium6.6 GHSA-4rh7-jwg9-m28m openssl-encrypt accepts refresh tokens as URL query parameters causing token leakage pip · openssl-encrypt 2026-04-01 medium6.6 GHSA-2vhw-q7vh-7xv2 openssl-encrypt's readiness endpoint leaks database error details to unauthenticated callers pip · openssl-encrypt 2026-04-01 medium6.6 GHSA-hvc7-763r-4f3h openssl-encrypt has no owner verification on key revocation — any client can revoke any key pip · openssl-encrypt 2026-04-01 medium6.6 GHSA-8h88-gxp3-j7pg openssl-encrypt's unverified key bundle from_dict() + to_identity() path allows encryption to attacker keys pip · openssl-encrypt 2026-04-01 medium6.6 GHSA-425g-fjhq-5h92 openssl-encrypt silently skips schema validation when jsonschema library is not installed pip · openssl-encrypt 2026-03-31 medium6.6 GHSA-vfgx-5q85-58q3 openssl-encrypt has non-cryptographic PRNG used for steganography pixel selection pip · openssl-encrypt 2026-03-31 medium6.6 GHSA-h3m5-p59h-x88p openssl-encrypt has visible password in process list via --password CLI argument pip · openssl-encrypt 2026-03-31 critical9.1 GHSA-h45m-mgcp-q388 openssl-encrypt: TOTP rate limiter is in-memory only — not shared across workers, lost on restart pip · openssl-encrypt 2026-03-31 medium6.6 GHSA-j48q-4c78-rhf9 openssl-encrypt: Dynamic .so loading for Whirlpool uses broad glob pattern without integrity verification pip · openssl-encrypt 2026-03-31 critical9.8 CVE-2026-27459 pyOpenSSL is a Python wrapper around the OpenSSL library. pip · pyopenssl 2026-03-16 medium5.3 CVE-2026-27448 pyOpenSSL allows TLS connection bypass via unhandled callback exception in set_tlsext_servername_callback pip · pyopenssl 2026-03-16 medium6.5 CVE-2026-2673 Issue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected preferred key exchange group when its key exchange group configuration includes the… openssl · openssl, siemens · simatic_cn_4100_firmware 2026-03-13 medium5.3 CVE-2026-22796 Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without fi… openssl · openssl 2026-01-27 medium5.5 CVE-2026-22795 Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file. openssl · openssl 2026-01-27 high7.5 CVE-2025-69421 Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function. openssl · openssl 2026-01-27 high7.5 CVE-2025-69420 Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first vali… openssl · openssl 2026-01-27 high7.4 CVE-2025-69419 Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII … openssl · openssl 2026-01-27 medium4.0 CVE-2025-69418 Issue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 1… openssl · openssl 2026-01-27 medium4.7 CVE-2025-68160 Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-ba… openssl · openssl 2026-01-27 medium5.9 CVE-2025-66199 Issue summary: A TLS 1.3 connection using certificate compression can be forced to allocate a large buffer before decompression without checking against the co… openssl · openssl 2026-01-27 medium5.5 CVE-2025-15469 Issue summary: The 'openssl dgst' command-line tool silently truncates input data to 16MB when using one-shot signing algorithms and reports success instead of… openssl · openssl 2026-01-27 medium5.9 CVE-2025-15468 Issue summary: If an application using the SSL_CIPHER_find() function in a QUIC protocol client or server receives an unknown cipher suite from the peer, a NUL… openssl · openssl 2026-01-27 medium6.1 CVE-2025-11187 Issue summary: PBMAC1 parameters in PKCS#12 files are missing validation which can trigger a stack-based buffer overflow, invalid pointer or NULL pointer deref… openssl · openssl 2026-01-27 critical9.8 CVE-2025-15467 Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. openssl · openssl, OpenSSL · OpenSSL 2026-01-27 high7.5 CVE-2025-59464 A memory leak in Node.js’s OpenSSL integration occurs when converting `X.509` certificate fields to UTF-8 without freeing the allocated buffer. nodejs · node.js 2026-01-20 high8.1 CVE-2025-67900 NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable. NXLog Agent 2025-12-14 medium4.3 CVE-2025-65500 NULL pointer dereference in coap_dtls_generate_cookie() in src/coap_openssl.c in OISM libcoap 4.3.5 allows remote attackers to cause a denial of service via a … libcoap · libcoap 2025-11-24 medium4.3 CVE-2025-65499 Array index error in tls_verify_call_back() in src/coap_openssl.c in OISM libcoap 4.3.5 allows remote attackers to cause a denial of service via a crafted DTLS… libcoap · libcoap 2025-11-24

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.