Certificate Name Authorization Bypass
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2023.8.13, 2025.12.1, 2026.0.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2023.8.13, 2025.12.1, 2026.0.1.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Data gap: No advisory context yet
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9/10CVSS 9.0
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
CVE-2026-115732 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.0 (critical) and affects Puppet Enterprise; fixed in 2023.8.13, 2025.12.1 and 2026.0.1.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- Fix
- Fixed in 2023.8.13, 2025.12.1, 2026.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Puppet Server, which uses the trapperkeeper-authorization component, is affected. A client with a CA-signed certificate whose name is a slight variation of an authorized hostname can be treated as that host, allowing it to impersonate other nodes and, in Puppet Enterprise, reach certificate authority administration and run commands on managed nodes.
Read the original description
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.
What to do
Upgrade to a fixed version: 2023.8.13, 2025.12.1, 2026.0.1.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Perforce Puppet Enterprise
From 2023.8.0 · fixed in 2023.8.13; From 2025.0.0 · fixed in 2025.12.1; From 2026.0.0 · fixed in 2026.0.1
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-115732
Is CVE-2026-115732 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-115732?
Puppet Enterprise: from 2023.8.0 before 2023.8.13; from 2025.0.0 before 2025.12.1; from 2026.0.0 before 2026.0.1.Source: cve.now feed data
How do I fix CVE-2026-115732?
Upgrade to a fixed version: 2023.8.13, 2025.12.1, 2026.0.1.Source: cve.now feed data