NetSight

Security Dashboard

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

Reset
22 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.6 CVE-2026-12564 A flaw was found in the AAP Controller's HashiCorp Vault credential plugin. Red Hat · Red Hat Ansible Automation Platform 2.4 for RHEL 8, Red Hat · Red Hat Ansible Automation Platform 2.4 for RHEL 9, Red Hat · Red Hat Ansible Automation Platform 2.5 for RHEL 8 +4 2026-08-18 critical GHSA-hcfh-22r5-mc4r Malware in @hashicorp-internal/vault-reportingMalware npm · @hashicorp-internal/vault-reporting 2026-02-06 critical9.1 CVE-2025-6000 Hashicorp Vault has Code Execution Vulnerability via Plugin Configuration go · github.com/hashicorp/vault 2025-08-01 critical9.8 CVE-2024-3817 HashiCorp go-getter Vulnerable to Argument Injection When Fetching Remote Default Git Branches go · github.com/hashicorp/go-getter 2024-04-17 critical9.9 CVE-2023-1782 HashiCorp Nomad vulnerable to unauthenticated client agent HTTP request privilege escalation go · github.com/hashicorp/nomad 2023-04-05 critical9.1 CVE-2022-40186 HashiCorp Vault vulnerable to incorrect metadata access go · github.com/hashicorp/vault 2022-09-22 critical9.9 CVE-2022-36130 HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated with the correct scopes, allowing potent… hashicorp · boundary 2022-09-01 critical9.1 CVE-2022-36129 HashiCorp Vault Enterprise 1.7.0 through 1.9.7, 1.10.4, and 1.11.0 clusters using Integrated Storage expose an unauthenticated API endpoint that could be abuse… hashicorp · vault 2022-07-26 critical9.8 CVE-2022-30324 Privilege escalation in Hashicorp Nomad go · github.com/hashicorp/nomad 2022-06-02 critical9.8 CVE-2022-26945 HashiCorp go-getter command injection go · github.com/hashicorp/go-getter, go · github.com/hashicorp/go-getter/v2, go · github.com/hashicorp/go-getter/s3/v2 +1 2022-05-25 critical9.1 CVE-2021-43998 HashiCorp Vault Incorrect Permission Assignment for Critical Resource go · github.com/hashicorp/vault 2021-11-30 critical9.8 CVE-2021-38553 HashiCorp Vault underlying database had excessively broad filesystem permissions from v1.4.0 until v1.8.0 go · github.com/hashicorp/vault 2021-08-13 critical9.8 CVE-2021-30476 HashiCorp Terraform’s Vault Provider (terraform-provider-vault) did not correctly configure GCE-type bound labels for Vault’s GCP auth method. hashicorp · terraform_provider 2021-04-22 critical9.8 CVE-2020-35192 The official vault docker images before 0.11.6 contain a blank password for a root user. hashicorp · vault 2020-12-17 critical9.8 CVE-2020-29564 The official Consul Docker images 0.7.1 through 1.4.2 contain a blank password for a root user. hashicorp · consul_docker_image 2020-12-08 critical9.1 CVE-2020-27195 Use After Free in HashiCorp Nomad go · github.com/hashicorp/nomad 2020-10-22 critical9.8 CVE-2020-25816 Token leases could outlive their TTL in HashiCorp Vault go · github.com/hashicorp/vault 2020-09-30 critical9.8 CVE-2020-12757 Improper Input Validation in HashiCorp Vault go · github.com/hashicorp/vault-plugin-secrets-gcp 2020-06-10 critical9.1 CVE-2020-10661 HashiCorp Vault Improper Privilege Management go · github.com/hashicorp/vault 2020-03-23 critical9.8 CVE-2020-7956 Improper Certificate Validation in HashiCorp Nomad go · github.com/hashicorp/nomad 2020-01-31 critical9.8 CVE-2019-12618 Hashicorp Nomad Access Control Issues go · github.com/hashicorp/nomad 2019-08-12 critical9.8 CVE-2018-9057 aws/resource_aws_iam_user_login_profile.go in the HashiCorp Terraform Amazon Web Services (AWS) provider through v1.12.0 has an inappropriate PRNG algorithm an… go · github.com/hashicorp/terraform-provider-aws 2018-03-27

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.