NetSight

Security Dashboard

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

Reset
244 matching advisories · page 2 of 9Index updated 8 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2026-46590 Apache Camel-PQC: The HashiCorp Vault and AWS Secrets Manager key-lifecycle managers deserialize persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter (incomplete remediation of CVE-2026-40048) maven · org.apache.camel:camel-pqc 2026-07-06 medium4.4 CVE-2026-5051 HashiCorp Vault and Vault Enterprise prior to 2.0.1 audit device validation logic did not consistently apply plugin directory protections when the legacy file … HashiCorp Vault and Vault Enterprise 2026-07-01 medium6.0 CVE-2026-8052 HashiCorp Nomad’s exec2 task driver prior to 0.1.2 is vulnerable to arbitrary file read and write on the client host as the Nomad process user through a symlin… go · github.com/hashicorp/nomad-driver-exec2 2026-05-12 high8.8 CVE-2026-7474 HashiCorp Nomad and Nomad Enterprise prior to 2.0.1 are vulnerable to code execution on the client host through a path traversal attack. go · github.com/hashicorp/nomad 2026-05-12 medium6.0 CVE-2026-6959 HashiCorp Nomad and Nomad Enterprise prior to 2.0.1 are vulnerable to arbitrary file read and write on the client host as the Nomad process user through a syml… go · github.com/hashicorp/nomad 2026-05-12 high7.5 CVE-2026-7776 Boundary Community Edition and Boundary Enterprise (“Boundary”) workers are vulnerable to a denial-of-service condition during node enrollment TLS handshakes. go · github.com/hashicorp/boundary 2026-05-04 high7.5 CVE-2026-5807 Vault is vulnerable to a denial-of-service condition where an unauthenticated attacker can repeatedly initiate or cancel root token generation or rekey operati… go · github.com/hashicorp/vault 2026-04-17 medium5.3 CVE-2026-5052 Vault’s PKI engine’s ACME validation did not reject local targets when issuing http-01 and tls-alpn-01 challenges. go · github.com/hashicorp/vault 2026-04-17 high7.5 CVE-2026-4525 If a Vault auth mount is configured to pass through the "Authorization" header, and the "Authorization" header is used to authenticate to Vault, Vault forwarde… go · github.com/hashicorp/vault 2026-04-17 high8.1 CVE-2026-3605 An authenticated user with access to a kvv2 path through a policy containing a glob may be able to delete secrets they were not authorized to read or write, re… go · github.com/hashicorp/vault 2026-04-17 high7.5 CVE-2026-4660 HashiCorp’s go-getter library up to v1.8.5 may allow arbitrary file reads on the file system during certain git operations through a maliciously crafted URL. go · github.com/hashicorp/go-getter 2026-04-09 medium6.8 CVE-2026-2808 Consul is vulnerable to arbitrary file read when configured with Kubernetes authentication go · github.com/hashicorp/consul 2026-03-12 critical GHSA-hcfh-22r5-mc4r Malware in @hashicorp-internal/vault-reportingMalware npm · @hashicorp-internal/vault-reporting 2026-02-06 high8.2 CVE-2025-68476 KEDA has Arbitrary File Read via Insufficient Path Validation in HashiCorp Vault Service Account Credential go · github.com/kedacore/keda/v2 2025-12-22 medium4.3 CVE-2025-67642 Jenkins HashiCorp Vault Plugin exposes system-scoped Vault credentials maven · com.datapipe.jenkins.plugins:hashicorp-vault-plugin 2025-12-10 medium4.3 CVE-2025-13432 Terraform state versions can be created by a user with specific but insufficient permissions in a Terraform Enterprise workspace. hashicorp · terraform 2025-11-21 high7.4 CVE-2025-13357 Vault’s Terraform Provider incorrectly set default deny_null_bind parameter for LDAP auth method to false by default go · github.com/hashicorp/terraform-provider-vault 2025-11-21 medium6.5 CVE-2025-11375 Consul event endpoint is vulnerable to denial of service go · github.com/hashicorp/consul 2025-10-28 medium6.5 CVE-2025-11374 Consul key/value endpoint is vulnerable to denial of service go · github.com/hashicorp/consul 2025-10-28 high7.5 CVE-2025-12044 Hashicorp Vault and Vault Enterprise vulnerable to a denial of service when processing JSON go · github.com/hashicorp/vault 2025-10-23 high8.1 CVE-2025-11621 HashiCorp Vault and Vault Enterprise's AWS Auth method may be susceptible to authentication bypass go · github.com/hashicorp/vault 2025-10-23 high7.5 CVE-2025-6203 HashiCorp Vault Community Edition Denial of Service Though Complex JSON Payloads go · github.com/hashicorp/vault 2025-08-28 high7.5 CVE-2025-8959 HashiCorp go-getter Vulnerable to Symlink Attacks go · github.com/hashicorp/go-getter 2025-08-15 medium6.5 CVE-2025-6013 HashiCorp Vault ldap auth method may not have correctly enforced MFA go · github.com/hashicorp/vault 2025-08-06 medium6.8 CVE-2025-6037 Hashicorp Vault has Incorrect Validation for Non-CA Certificates go · github.com/hashicorp/vault 2025-08-01 medium5.7 CVE-2025-6015 Hashicorp Vault has Login MFA Rate Limit Bypass Vulnerability go · github.com/hashicorp/vault 2025-08-01 medium6.5 CVE-2025-6014 Hashicorp Vault's TOTP Secrets Engine Susceptible to Code Reuse go · github.com/hashicorp/vault 2025-08-01 low3.7 CVE-2025-6011 Hashicorp Vault has an Observable Discrepancy on Existing and Non-Existing Users go · github.com/hashicorp/vault 2025-08-01 medium5.3 CVE-2025-6004 Hashicorp Vault has Lockout Feature Authentication Bypass go · github.com/hashicorp/vault 2025-08-01 critical9.1 CVE-2025-6000 Hashicorp Vault has Code Execution Vulnerability via Plugin Configuration go · github.com/hashicorp/vault 2025-08-01

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.