Skip to content

Product

ubuntu/puppet vulnerabilities

15 published CVES affecting ubuntu/puppet, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
15
Critical
2
High
5
Medium
8
Low
0
Unscored
0
CISA KEV
1

Latest ubuntu/puppet CVEs

Newest publication first

  1. CriticalCVSS 9.4 EPSS 0.69% CISA KEV added 2026-11-17 Exploited in the wild PoC

    Deserialization of untrusted data in the report-processing code of Puppet, as used by Puppet Server, in the affected releases, allows a client that holds any CA-signed agent certificate to execute arbitrary code on the Puppet Server as its service user by submitting a report cont...

  2. MediumCVSS 4.9 EPSS 0.92%

    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 not be. This issue only affects SSH/WinRM nodes (inventory service nodes).

  3. HighCVSS 7.5 EPSS 0.54%

    The mechanism which performs certificate validation was discovered to have a flaw that resulted in certificates signed by an internal certificate authority to not be properly validated. This issue only affects clients that are configured to utilize Tenable.sc as the vulnerability...

  4. HighCVSS 7.5 EPSS 7.7% Scanner template

    Puppet Server and PuppetDB provide useful performance and debugging information via their metrics API endpoints. For PuppetDB this may contain things like hostnames. Puppet Server reports resource names and titles for defined types (which may contain sensitive information) as wel...

  5. MediumCVSS 6.5 EPSS 0.89%

    The default vhost configuration file in Puppet before 3.6.2 does not include the SSLCARevocationCheck directive, which might allow remote attackers to obtain sensitive information via a revoked certificate when a Puppet master runs with Apache 2.4.

  6. HighCVSS 8.2 EPSS 2.8%

    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. This could be used to force YAML deserialization in an unsafe manner, which would lead to remote code execution. This change constr...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.