CVE-2026-115732
Certificate Name Authorization Bypass
No known exploitation. EPSS puts it in the 55th percentile. Fixed versions are out.
No public exploit knownFix1 product3 fixed builds listed below
e.g. OID 1.3.6.1.4.1.25623.1.0.180981
What to do
Find your product and version, then upgrade to the build on the right.
- Perforce Puppet EnterpriseAffected: ≥ 2023.8.0, < 2023.8.13Upgrade to: 2023.8.13Affected: ≥ 2025.0.0, < 2025.12.1Upgrade to: 2025.12.1Affected: ≥ 2026.0.0, < 2026.0.1Upgrade to: 2026.0.1Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Ask your Puppet administrator to confirm which Puppet Enterprise version you're running.
- Check whether your certificate-signing process uses autosign or broad approval policies that could let a colliding certificate name get issued.
- Upgrade to the fixed version for your branch: 2023.8.13, 2025.12.1, or 2026.0.1.
- After upgrading, review certificate requests and node names for anything suspicious or unexpected.
What it is
From the CVE record
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.
In plain language
Written by AI from the recordA flaw in Puppet Enterprise could let a node with a similarly-named certificate impersonate another trusted node, but it's not being exploited and a fix is already available, so this is a plan-to-patch item, not an emergency.
Incorrect authorization in trapperkeeper-authorization's certificate-name matching lets a holder of a CA-signed certificate whose name is a prefix/suffix of an authorized hostname be authorized as that host, enabling node impersonation, CA-admin access, and remote command execution on managed nodes in Puppet Enterprise.
If you're affected
- Managed server takeover
- Impersonation of trusted nodes
- Certificate authority admin access
- Remote command execution on infrastructure
- Operational disruption
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.7% chance of exploitation activity in the next 30 days, which ranks it in the 55th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
- Attention now
Sustained, driven by wide press coverage.
Lifecycle
8 events over 6 days, from the signal feeds we watch.
- OpenVAS check added
- Patch availablerecord updated
- Patch availablepublished, weakness classified, att&ck mapped, record updated
Affected products
Technical detail
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Puppet Enterprise, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI