NetSight

Security Dashboard

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

Reset
38 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.3 CVE-2026-118977 Authorization bypass through a user-controlled key in the PuppetDB facts terminus used by Puppet Server allows a client holding any valid agent certificate to … Perforce · Puppet Enterprise, Perforce · Puppet Core 2 days ago high7.1 CVE-2026-91938 Flowise versions before 3.1.4 contain a server-side request forgery vulnerability in Cheerio, Playwright, and Puppeteer document loader nodes that bypass SSRF … Flowise 2026-09-15 high8.6 CVE-2026-85979 Affected versions of Puppet Enterprise contain a command injection vulnerability. Puppet Enterprise 2026-09-11 high8.8 CVE-2025-5459 A user with specific node group editing permissions and a specially crafted class parameter could be used to execute commands as root on the primary host. puppet · puppet_enterprise 2025-06-26 high7.3 CVE-2024-27294 dp-golang is a Puppet module for Go installations. danielparks · dp-golang 2024-02-29 high7.4 CVE-2022-25350 All versions of the package puppet-facter are vulnerable to Command Injection via the getFact function due to improper input sanitization. npm · puppet-facter 2023-01-26 high8.4 CVE-2022-3276 Command injection is possible in the puppetlabs-mysql module prior to version 13.0.0. puppet · puppetlabs-mysql 2022-10-07 high8.4 CVE-2022-3275 Command injection is possible in the puppetlabs-apt module prior to version 9.0.0. puppet · puppetlabs-mysql, fedoraproject · fedora 2022-10-07 high8.1 CVE-2021-27024 A flaw was discovered in Continuous Delivery for Puppet Enterprise (CD4PE) that results in a user with lower privileges being able to access a Puppet Enterpris… puppet · continuous_delivery 2021-11-18 high8.8 CVE-2021-27020 Puppet Enterprise presented a security risk by not sanitizing user input when doing a CSV export. puppet · puppet_enterprise 2021-08-30 high7.5 CVE-2021-27018 The mechanism which performs certificate validation was discovered to have a flaw that resulted in certificates signed by an internal certificate authority to … puppet · remediate 2021-08-30 high8.8 CVE-2021-27021 A flaw was discovered in Puppet DB, this flaw results in an escalation of privileges which allows the user to delete tables via an SQL query. puppet · puppet, puppet · puppet_enterprise, puppet · puppetdb 2021-07-20 high7.7 CVE-2020-7944 In Continuous Delivery for Puppet Enterprise (CD4PE) before 3.4.0, changes to resources or classes containing Sensitive parameters can result in the Sensitive … puppet · continuous_delivery 2020-03-26 high7.5 CVE-2020-7943 Puppet Server and PuppetDB provide useful performance and debugging information via their metrics API endpoints. puppet · puppet_enterprise, puppet · puppet_server, puppet · puppetdb 2020-03-11 high8.8 CVE-2015-5686 Parts of the Puppet Enterprise Console 3.x were found to be susceptible to clickjacking and CSRF (Cross-Site Request Forgery) attacks. puppet · puppet_enterprise 2020-02-27 high7.5 CVE-2018-6517 Improper Certificate Validation in chloride rubygems · chloride 2019-03-21 high7.8 CVE-2018-11748 Previous releases of the Puppet device_manager module creates configuration files containing credentials that are world readable. puppet · device_manager 2018-10-02 high8.6 CVE-2018-11746 In Puppet Discovery prior to 1.2.0, when running Discovery against Windows hosts, WinRM connections can fall back to using basic auth over insecure channels if… puppet · discovery 2018-07-03 high7.8 CVE-2018-6516 On Windows only, with a specifically crafted configuration file an attacker could get Puppet PE client tools (aka pe-client-tools) 16.4.x prior to 16.4.6, 17.3… puppet · puppet_enterprise_client_tools 2018-06-14 high7.8 CVE-2018-6515 Puppet Agent 1.10.x prior to 1.10.13, Puppet Agent 5.3.x prior to 5.3.7, and Puppet Agent 5.5.x prior to 5.5.2 on Windows only, with a specially crafted config… puppet · puppet 2018-06-11 high7.8 CVE-2018-6514 In Puppet Agent 1.10.x prior to 1.10.13, Puppet Agent 5.3.x prior to 5.3.7, Puppet Agent 5.5.x prior to 5.5.2, Facter on Windows is vulnerable to a DLL preload… puppet · puppet 2018-06-11 high8.8 CVE-2018-6513 Puppet Enterprise 2016.4.x prior to 2016.4.12, Puppet Enterprise 2017.3.x prior to 2017.3.7, Puppet Enterprise 2018.1.x prior to 2018.1.1, Puppet Agent 1.10.x … puppet · puppet, puppet · puppet_enterprise 2018-06-11 high7.1 CVE-2016-9599 puppet-tripleo before versions 5.5.0, 6.2.0 is vulnerable to an access-control flaw in the IPtables rules management, which allowed the creation of TCP/UDP rul… openstack · puppet-tripleo, redhat · openstack 2018-04-24 high8.0 CVE-2018-6508 Puppet Enterprise 2017.3.x prior to 2017.3.3 are vulnerable to a remote execution bug when a specially crafted string was passed into the facter_task or puppet… puppet · puppet_enterprise 2018-02-09 high7.5 CVE-2017-2297 Puppet Enterprise versions prior to 2016.4.5 and 2017.2.1 did not correctly authenticate users before returning labeled RBAC access tokens. puppet · puppet_enterprise 2018-02-01 high7.2 CVE-2016-5714 Puppet Enterprise 2015.3.3 and 2016.x before 2016.4.0, and Puppet Agent 1.3.6 through 1.7.0 allow remote attackers to bypass a host whitelist protection mechan… puppet · puppet_enterprise, puppet · puppet_agent 2017-10-18 high7.5 CVE-2017-2299 Versions of the puppetlabs-apache module prior to 1.11.1 and 2.1.0 make it very easy to accidentally misconfigure TLS trust. puppet · puppetlabs-apache 2017-09-15 high8.8 CVE-2016-5716 The console in Puppet Enterprise 2015.x and 2016.x prior to 2016.4.0 includes unsafe string reads that potentially allows for remote code execution on the cons… puppet · puppet_enterprise 2017-08-09 high7.5 CVE-2017-7529 Nginx versions since 0.5.6 up to and including 1.13.2 are vulnerable to integer overflow vulnerability in nginx range filter module resulting into leak of pote… f5 · nginx, puppet · puppet_enterprise, apple · xcode 2017-07-13 high8.2 CVE-2017-2295 Versions of Puppet prior to 4.10.1 will deserialize data off the wire (from the agent to the server, in this case) with a attacker-specified format. puppet · puppet, debian · debian_linux 2017-07-05

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.