NetSight

Security Dashboard

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

Reset
40 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.7 CVE-2026-54875 Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. openssl · openssl 53 days ago low3.7 CVE-2026-35191 Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvali… openssl · openssl 53 days ago low3.7 CVE-2026-77696 Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. openssl · openssl, OpenSSL · OpenSSL 53 days ago low3.7 CVE-2026-54872 Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementa… openssl · openssl, OpenSSL · OpenSSL 53 days ago low3.7 CVE-2026-78124 strongSwan 5.0.2 through 6.0.7 allows PKCS#7 certificate enumeration in the openssl plugin that leads to a lack of release of memory after its effective lifeti… strongswan · strongswan 2026-09-11 low3.5 CVE-2026-81717 openssl_encrypt (pip package openssl-encrypt) before 1.4.9 contains two weaknesses in the portable USB drive feature, whose threat model treats the removable d… jahlives · openssl_encrypt 2026-08-27 low3.3 CVE-2026-81715 openssl_encrypt (pip package openssl-encrypt) versions <= 1.4.8 do not redact the keyserver bearer token passed as the positional argument to 'keyserver set-to… jahlives · openssl_encrypt 2026-08-27 low3.3 CVE-2026-81696 openssl_encrypt versions before 1.4.9 fail to sanitize terminal control characters in file metadata printed by the info command. jahlives · openssl_encrypt 2026-08-27 low3.3 CVE-2026-81695 openssl_encrypt versions before 1.4.9 fail to escape attacker-controlled key_id values printed to stderr during decrypt auto-detection. jahlives · openssl_encrypt 2026-08-27 low3.3 CVE-2026-81694 openssl-encrypt (pip package, versions <= 1.4.8) fails to sanitize filenames read from untrusted drive data (outside the AES-GCM authenticated manifest) before… jahlives · openssl_encrypt 2026-08-27 low3.3 CVE-2026-81685 openssl_encrypt versions before 1.4.9 fail to sanitize recovery-slot metadata in the desktop GUI, allowing attackers to inject control characters and line sepa… jahlives · openssl_encrypt 2026-08-27 low3.7 CVE-2026-74887 openssl_encrypt before 1.4.0 imports Python's non-cryptographic 'random' module (Mersenne Twister PRNG) at line 15 of openssl_encrypt/modules/pqc.py. jahlives · openssl_encrypt 2026-08-17 low3.6 CVE-2026-74885 openssl_encrypt versions before 1.4.0 contain a logging bug in restore_hidden_modules() that logs module counts after clearing, always showing zero restored mo… jahlives · openssl_encrypt 2026-08-17 low3.3 CVE-2026-74870 openssl_encrypt (pip) versions <= 1.4.7 contain an information exposure vulnerability where the 'hsm fido2-test' and 'hsm onlykey-test' diagnostic commands unc… jahlives · openssl_encrypt 2026-08-17 low3.7 CVE-2026-42770 Issue summary: When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the peer key is not properly checked for the subgroup membership. openssl · openssl 2026-06-09 low3.7 CVE-2026-42768 Issue summary: The CMS_decrypt and PKCS7_decrypt functions are vulnerable to Bleichenbacher-style attack when an attacker is able to provide the CMS or S/MIME … openssl · openssl 2026-06-09 low1.8 CVE-2025-14575 An Uncontrolled Search Path Element vulnerability in the OpenSSL TLS backend of Qt Network (qtbase) in Qt Qt Framework (Unix) allows a local attacker to load a… 2026-05-19 low2.7 CVE-2025-41721 A high privileged remote attacker can influence the parameters passed to the openssl command due to improper neutralization of special elements when adding a p… 2025-10-22 low3.7 CVE-2025-60019 glib-networking's OpenSSL backend fails to properly check the return value of memory allocation routines. 2025-09-25 low3.4 CVE-2025-42927 SAP NetWeaver AS Java application uses Adobe Document Service, installed with a vulnerable version of OpenSSL.Successful exploitation of known vulnerabilities … 2025-09-09 low2.5 CVE-2025-23253 NVIDIA NvContainer service for Windows contains a vulnerability in its usage of OpenSSL, where an attacker could exploit a hard-coded constant issue by copying… 2025-04-22 low3.7 CVE-2025-3416 A flaw was found in OpenSSL's handling of the properties argument in certain functions. 2025-04-08 low GHSA-v8gr-m533-ghj9 Vulnerable OpenSSL included in cryptography wheels pip · cryptography 2023-09-21 low GHSA-jm77-qphf-c4w8 pyca/cryptography's wheels include vulnerable OpenSSL pip · cryptography 2023-08-01 low GHSA-5cpq-8wj7-hf2v Vulnerable OpenSSL included in cryptography wheels pip · cryptography 2023-06-02 low3.7 CVE-2021-23839 OpenSSL 1.0.2 supports SSLv2. openssl · openssl, oracle · business_intelligence, oracle · enterprise_manager_for_storage_management +5 2021-02-16 low3.7 CVE-2020-1968 The Raccoon attack exploits a flaw in the TLS specification which can lead to an attacker being able to compute the pre-master secret in connections which have… openssl · openssl, canonical · ubuntu_linux, debian · debian_linux +9 2020-09-09 low3.7 CVE-2019-1563 In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large numbe… openssl · openssl 2019-09-10 low3.3 CVE-2019-1552 OpenSSL has internal defaults for a directory tree where it can find a configuration file as well as certificates used for verification in TLS. openssl · openssl, OpenSSL · OpenSSL 2019-07-30 low3.7 CVE-2016-0701 The DH_check_pub_key function in crypto/dh/dh_check.c in OpenSSL 1.0.2 before 1.0.2f does not ensure that prime numbers are appropriate for Diffie-Hellman (DH)… openssl · openssl 2016-02-15

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.