NetSight

Security Dashboard

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

Reset
244 matching advisories · page 3 of 9Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.2 CVE-2025-5999 Hashicorp Vault has Privilege Escalation Vulnerability go · github.com/hashicorp/vault 2025-08-01 medium5.4 CVE-2025-34075 HashiCorp Vagrant has code injection vulnerability through default synced folders rubygems · vagrant 2025-07-02 low3.1 CVE-2025-4656 Vault Community Edition rekey and recovery key operations can cause denial of service go · github.com/hashicorp/vault 2025-06-25 high8.1 CVE-2025-4922 Hashicorp Nomad Incorrect Privilege Assignment vulnerability go · github.com/hashicorp/nomad 2025-06-11 high7.6 CVE-2025-3744 Nomad Enterprise (“Nomad”) jobs using the policy override option are bypassing the mandatory sentinel policies. hashicorp · nomad 2025-05-13 medium6.6 CVE-2025-3879 Hashicorp Vault Community vulnerable to Incorrect Authorization go · github.com/hashicorp/vault 2025-05-02 medium4.5 CVE-2025-4166 Hashicorp Vault Community vulnerable to Generation of Error Message Containing Sensitive Information go · github.com/hashicorp/vault 2025-05-02 medium6.5 CVE-2025-1296 Nomad is vulnerable to unintentional exposure of the workload identity token and client secret token in audit logs go · github.com/hashicorp/nomad 2025-03-10 high8.2 CVE-2025-1293 Hermes improperly validates a JWT go · github.com/hashicorp-forge/hermes 2025-02-20 high7.1 CVE-2025-0937 Nomad Community and Nomad Enterprise ("Nomad") event stream configured with a wildcard namespace can bypass the ACL Policy allowing reads on other namespaces. hashicorp · nomad 2025-02-12 medium6.6 GHSA-29qp-crvh-w22m Withdrawn Advisory: github.com/hashicorp/yamux's DefaultConfig has dangerous defaults causing hung Read go · github.com/hashicorp/yamux 2025-01-29 high7.5 CVE-2025-0377 HashiCorp go-slug Vulnerable to Zip Slip Attack go · github.com/hashicorp/go-slug 2025-01-21 medium6.5 CVE-2024-12678 Hashicorp Nomad Incorrect Privilege Assignment vulnerability go · github.com/hashicorp/nomad 2024-12-20 medium5.9 CVE-2024-12289 Boundary Community Edition Incorrectly Handles HTTP Requests On Initialization Which May Lead to a Denial of Service go · github.com/hashicorp/boundary 2024-12-12 high7.7 CVE-2024-10975 Hashicorp Nomad Incorrect Authorization vulnerability go · github.com/hashicorp/nomad 2024-11-07 high7.5 CVE-2024-8185 Hashicorp Vault vulnerable to denial of service through memory exhaustion go · github.com/hashicorp/vault, go · github.com/openbao/openbao 2024-10-31 medium6.1 CVE-2024-10086 Hashicorp Consul Cross-site Scripting vulnerability go · github.com/hashicorp/consul 2024-10-30 high8.3 CVE-2024-10006 Hashicorp Consul Improper Neutralization of HTTP Headers for Scripting Syntax vulnerability go · github.com/hashicorp/consul 2024-10-30 high8.1 CVE-2024-10005 Hashicorp Consul Path Traversal vulnerability go · github.com/hashicorp/consul 2024-10-30 low3.8 CVE-2024-10228 The Vagrant VMWare Utility Windows installer targeted a custom location with a non-protected path that could be modified by an unprivileged user, introducing p… hashicorp · vagrant_vmware_utility 2024-10-29 high7.2 CVE-2024-9180 Vault Community Edition privilege escalation vulnerability go · github.com/hashicorp/vault, go · github.com/openbao/openbao 2024-10-10 high7.5 CVE-2024-7594 Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default go · github.com/hashicorp/vault, go · github.com/openbao/openbao 2024-09-26 medium6.5 CVE-2024-8365 Vault Leaks Client Token and Token Accessor in Audit Devices go · github.com/hashicorp/vault 2024-09-02 low3.7 CVE-2024-43808 In JetBrains TeamCity before 2024.07.1 self XSS was possible in the HashiCorp Vault plugin jetbrains · teamcity 2024-08-16 medium5.8 CVE-2024-7625 Nomad Vulnerable to Allocation Directory Escape On Non-Existing File Paths Through Archive Unpacking go · github.com/hashicorp/nomad 2024-08-15 high7.7 CVE-2024-6717 HashiCorp Nomad is vulnerable to path escape through archive unpacking during migration go · github.com/hashicorp/nomad 2024-07-23 high7.5 CVE-2024-6468 Hashicorp Vault vulnerable to Improper Check or Handling of Exceptional Conditions go · github.com/hashicorp/vault 2024-07-11 high8.4 CVE-2024-6257 HashiCorp go-getter Vulnerable to Code Execution On Git Update Via Git Config Manipulation go · github.com/hashicorp/go-getter 2024-06-25 medium6.0 CVE-2024-6104 go-retryablehttp can leak basic auth credentials to log files go · github.com/hashicorp/go-retryablehttp 2024-06-24 low2.6 CVE-2024-5798 HashiCorp Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims go · github.com/hashicorp/vault 2024-06-12

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.