VulnTideExploited vulnerabilities, by vendor. Data as of .
Not in CISA KEVReported exploited: VulnCheck KEV since Published CVSS 9.0 criticalEPSS 0.7% probability of exploitation in 30 days
Perforce

CVE-2026-115732: Certificate Name Authorization Bypass

Is it exploited?

Reported, not confirmed by CISA. VulnCheck KEV lists it as exploited in the wild. CISA has not added it to its Known Exploited Vulnerabilities catalog as of .

VulnCheck KEV lists it since . It cites 1 public report, the first from .

How likely is exploitation in the next 30 days?
0.7%

EPSS score, percentile 55.3 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?
9.0 Critical

CVSS v4.0 base score, given by the CNA

What should I do?

Upgrade to Puppet Enterprise 2023.8.13, 2025.12.1, or 2026.0.1 as applicable. Full textSolution from the CVE record.

CISA has set no required action, because the vulnerability is not in KEV.

No patch or vendor advisory is listed in the CVE record. Check Perforce's advisories.

Which versions are affected?

Affected

  • from 2023.8.0 to before 2023.8.13
  • from 2025.0.0 to before 2025.12.1
  • from 2026.0.0 to before 2026.0.1

Unaffected 2023.8.13; 2025.12.1; 2026.0.1

Versions by product

Source: CISA KEV 2026.11.10, as of ; VulnCheck KEV, as of ; FIRST EPSS, as of ; CVE List, as of . About the data.

Description

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.

Source: CVE List, as of . About the data.

What to do

Advisories and patches

No patch, vendor advisory or mitigation is listed in the CVE record. Check Perforce's own security advisories for a fix, and compare your version with the affected versions below.

Solution (from the CVE record)

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.

This summary is based on the CVE record as of . Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

Versions by product, as listed in the CVE record (1 product)
Perforce Puppet Enterprise
StatusVersions
Affectedfrom 2023.8.0 to before 2023.8.13
Affectedfrom 2025.0.0 to before 2025.12.1
Affectedfrom 2026.0.0 to before 2026.0.1
Unaffected2023.8.13
Unaffected2025.12.1
Unaffected2026.0.1

Versions not listed are: affected.

Versions the record lists as unaffected: 2023.8.13, 2025.12.1, 2026.0.1.

Source: CVE List, as of . About the data.

Weakness

CWE-863, CWE-697, 2 CAPEC

Attack patterns (CAPEC)

CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record.

Timeline

DateEvent
CVE record published
CVE record last updated

References

1