VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

puppet: vulnerability history, versions and safety

puppet is a package in the Debian ecosystem. Vulert records 80 vulnerabilities for it across 6 releases, from Oct 2009 to Nov 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
80 vulnerabilities recorded U80
i
6 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all puppet vulnerabilities

Vulert verdict on puppet i

Updated on 23 Oct 2026

Careful: 6 of the 80 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 80 vulnerabilities on record across 12 years, none in the last year.

What to do: Plan around the 6 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 80 over 12 years · 0 in the last year i
  • Latest disclosure 18 Nov 2021 i
  • Highest CVSS 9.8 i
  • With no published fix 6 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for puppet, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
6.16.0-1 U6 No Details →
5.5.22-4 U6 No Details →
5.5.22-3 U6 No Details →
5.5.22-2.2 U6 No Details →
5.5.22-2.1 U6 No Details →
5.5.22-2 U6 No Details →

Newest 6 of 6 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2009 2
  • 2010 2
  • 2011 10
  • 2012 24
  • 2013 22
  • 2014 4
  • 2017 8
  • 2018 2
  • 2020 2
  • 2021 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 80 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for puppet

The 5 most severe of 80 vulnerabilities recorded for this package

Search all 80 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Unauthorized Code Execution Risk in Puppet Agent - CVE-2016-5713 9.8 critical 4.7.0-1 06 Dec 2017
Critical HTTP Credential Leak in Puppet Package 9.8 critical No fix published 18 Nov 2021
Remote Code Execution Vulnerability in Puppet Prior to 4.10.1 8.2 high 4.8.2-5 05 Jul 2017
Puppet Execution Protocol Command Whitelist Bypass in Puppet Package 7.2 high 4.8.0-1 18 Oct 2017
Vulnerability in Puppet Package (CVE-2020-7942) 6.5 medium No fix published 19 Feb 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About puppet

Is puppet safe to use?

Vulert records 80 vulnerabilities for puppet in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 80 not yet rated. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does puppet have?

80 vulnerabilities are recorded for puppet in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 80 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new puppet vulnerabilities disclosed?

0 vulnerabilities were recorded for puppet in the last 12 months, and the oldest entry in this database dates to 06 Oct 2009. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of puppet are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor puppet for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the puppet version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.