NetSight

Security Dashboard

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

Reset
82 matching advisories · page 1 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2026-66379 An authenticated user may view private Puppet module metadata without repository read access. jfrog · artifactory 2026-08-12 medium6.7 CVE-2026-8804 Puppet resource_api (shipped in Puppet Core 8.x and Puppet Enterprise 2023.8.x and 2025.x) does not preserve the sensitive flag on parameters defined via the r… 2026-07-03 medium6.9 CVE-2025-10360 In Puppet Enterprise versions 2025.4.0 and 2025.5, the encryption key used for encrypting content in the Infra Assistant database was not excluded from the fil… 2025-09-24 medium6.5 CVE-2024-36527 puppeteer-renderer v.3.2.0 and before is vulnerable to Directory Traversal. 2024-06-17 medium6.2 CVE-2024-3716 A flaw was found in foreman-installer when puppet-candlepin is invoked cpdb with the --password parameter. redhat · satellite 2024-06-05 medium6.8 CVE-2023-5309 Versions of Puppet Enterprise prior to 2021.7.6 and 2023.5 contain a flaw which results in broken session management for SAML implementations. puppet · puppet_enterprise 2023-11-07 medium4.4 CVE-2023-5255 For certificates that utilize the auto-renew feature in Puppet Server, a flaw exists which prevents the certificates from being revoked. puppet · puppet_enterprise, puppet · puppet_server 2023-10-03 medium5.3 CVE-2023-1894 A Regular Expression Denial of Service (ReDoS) issue was discovered in Puppet Server 7.9.2 certificate validation. puppet · puppet_enterprise, puppet · puppet_server 2023-05-04 medium4.1 CVE-2022-2394 Puppet Bolt prior to version 3.24.0 will print sensitive parameters when planning a run resulting in them potentially being logged when run programmatically, s… perforce · puppet_bolt 2022-07-19 medium5.6 CVE-2022-0675 In certain situations it is possible for an unmanaged rule to exist on the target system that has the same comment as the rule specified in the manifest. puppet · firewall 2022-03-02 medium4.4 CVE-2021-27026 A flaw was divered in Puppet Enterprise and other Puppet products where sensitive plan parameters may be logged puppet · puppet, puppet · puppet_connect, puppet · puppet_enterprise 2021-11-18 medium6.5 CVE-2021-27025 A flaw was discovered in Puppet Agent where the agent may silently ignore Augeas settings or may be vulnerable to a Denial of Service condition prior to the fi… rubygems · puppet 2021-11-18 medium4.9 CVE-2021-27022 A flaw was discovered in bolt-server and ace where running a task with sensitive parameters results in those sensitive parameters being logged when they should… puppet · puppet, puppet · puppet_enterprise 2021-09-07 medium4.3 CVE-2021-27019 PuppetDB logging included potentially sensitive system information. puppet · puppet_enterprise, puppet · puppetdb 2021-08-30 medium5.5 CVE-2020-7945 Local registry credentials were included directly in the CD4PE deployment definition, which could expose these credentials to users who should not have access … puppet · continuous_delivery 2020-09-18 medium6.5 CVE-2020-7942 Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate al… rubygems · puppet 2020-02-19 medium5.4 CVE-2018-11751 Previous versions of Puppet Agent didn't verify the peer in the SSL connection prior to downloading the CRL. puppet · puppet_server 2019-12-16 medium6.5 CVE-2019-10695 When using the cd4pe::root_configuration task to configure a Continuous Delivery for PE installation, the root user’s username and password were exposed in the… puppet · continuous_delivery 2019-12-12 medium6.1 CVE-2013-4968 Puppet Enterprise before 3.0.1 allows remote attackers to (1) conduct clickjacking attacks via unspecified vectors related to the console, and (2) conduct cros… puppet · puppet_enterprise 2019-12-11 medium5.9 CVE-2015-1855 verify_certificate_identity in the OpenSSL extension in Ruby before 2.0.0 patchlevel 645, 2.1.x before 2.1.6, and 2.2.x before 2.2.2 does not properly validate… ruby-lang · ruby, ruby-lang · trunk, debian · debian_linux +2 2019-11-29 medium6.5 CVE-2019-5786 Use-After-Free in puppeteerExploited npm · puppeteer 2019-06-27 medium5.5 CVE-2018-11752 Previous releases of the Puppet cisco_ios module output SSH session debug information including login credentials to a world readable file on every run. puppet · cisco_ios 2018-10-02 medium6.5 CVE-2018-11750 Previous releases of the Puppet cisco_ios module did not validate a host's identity before starting a SSH connection. puppet · cisco_ios_module 2018-10-02 medium5.4 CVE-2018-6511 A cross-site scripting vulnerability in Puppet Enterprise Console of Puppet Enterprise allows a user to inject scripts into the Puppet Enterprise Console when … puppet · puppet_enterprise 2018-05-08 medium5.4 CVE-2018-6510 A cross-site scripting vulnerability in Puppet Enterprise Console of Puppet Enterprise allows a user to inject scripts into the Puppet Enterprise Console when … puppet · puppet_enterprise 2018-05-08 medium6.5 CVE-2016-9590 puppet-swift before versions 8.2.1, 9.4.4 is vulnerable to an information-disclosure in Red Hat OpenStack Platform director's installation of Object Storage (s… openstack · puppet-swift, redhat · openstack 2018-04-26 medium6.5 CVE-2017-10690 In previous versions of Puppet Agent it was possible for the agent to retrieve facts from an environment that it was not classified to retrieve from. puppet · puppet, puppet · puppet_enterprise, redhat · satellite 2018-02-09 medium5.5 CVE-2017-10689 In previous versions of Puppet Agent it was possible to install a module with world writable permissions. rubygems · puppet 2018-02-09 medium6.5 CVE-2017-2296 In Puppet Enterprise 2017.1.x and 2017.2.1, using specially formatted strings with certain formatting characters as Classifier node group names or RBAC role di… puppet · puppet_enterprise 2018-02-01 medium4.9 CVE-2017-2293 Versions of Puppet Enterprise prior to 2016.4.5 or 2017.2.1 shipped with an MCollective configuration that allowed the package plugin to install or remove arbi… puppet · puppet_enterprise 2018-02-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.