Perforce Puppet Enterprise
Certificate Name Authorization Bypass
Incorrect authorization in the certificate-name matching of trapperkeeper-authorization, as used by Puppet Server, in the affected products, allows a client that holds a CA-signed certificate whose name extends or shortens an authorized hostname to be authorized as that host. This enables impersonation of other nodes and, in Puppet Enterprise, access to certificate-authority administration and remote command execution on managed nodes. Exploitation requires a certificate with a colliding name, which the certificate authority issues by approval or autosign.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2023.8.0, < 2023.8.13
- >= 2025.0.0, < 2025.12.1
- >= 2026.0.0, < 2026.0.1
Fixed in 2023.8.13, 2025.12.1, 2026.0.1
Mitigation
Upgrade to Puppet Enterprise 2023.8.13, 2025.12.1, or 2026.0.1 as applicable. The fix ships to every service that uses the library.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 informational
Informational 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| foxcornlab/puppet-enterprise-scanner | 18 Nov 2026 +14 d | 18 Nov 2026 | 0 | Informational · detection |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.