Skip to content
Breach Index · running record

Perforce (Puppet) vulnerabilities in 2026: CVE-2026-115731 and CVE-2026-115732 (not a breach of Perforce)

Perforce owns Puppet, the configuration-management software many large companies use to push settings and software to their servers. A Puppet Server can change every machine it manages, so a flaw in it reaches all of them. This page tracks the November 2026 Puppet Server flaws, including the community fork OpenVox, and keeps the vendors' fixes apart from CISA's exploitation listing.

Short answer

Was Perforce hacked?

No, CVE-2026-115731 is not a breach of Perforce: nothing reported shows an intrusion at Perforce or at the OpenVox project. It is a vulnerability in Puppet's report-processing code, as used by Puppet Server. Per the CVE record Perforce published on 3 November 2026, a client holding any CA-signed agent certificate can run code on the Puppet Server by submitting a crafted report, and where the CA autosigns without strong verification an unauthenticated attacker can obtain such a certificate (CVSS v4.0 9.4).

CISA added it to the Known Exploited Vulnerabilities catalog with a date added of 17 November 2026 and a due date of 1 December 2026, without public detail of the attacks. Fixes: Puppet Enterprise 2023.8.13, 2025.12.1 and 2026.0.1; Puppet Core 8.22.2 and 9.1.3; OpenVox Server 9.2.0 and 8.18.0 and Agent 9.3.0 and 8.32.0.

Timeline at a glance

  1. 3 Nov 2026Perforce and OpenVox fix CVE-2026-115731 (RCE, CVSS v4.0 9.4) and CVE-2026-115732 (authorization bypass, 9.0), reported by Neodyme. (Perforce (CVE record))Not a breach
  2. 3 Nov 2026OpenVox: Server 9.2.0/8.18.0, Agent 9.3.0/8.32.0; open source Puppet will not receive security updates. (OpenVox)Not a breach
  3. 17 Nov 2026CISA adds CVE-2026-115731 to the Known Exploited Vulnerabilities catalog, due 1 December 2026. (CISA)Not a breach

Last updated 19 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.

Perforce (Puppet) incident timeline, in detail

Confirmed = acknowledged by Perforce (Puppet), a regulator filing or a court. Reported = credible reporting Perforce (Puppet) has not fully confirmed. Unverified claim = an attacker or leak-site claim.

Nov 2026Not a breachProduct vulnerability (server side), known exploited

CVE-2026-115731: Puppet Server report deserialization RCE, known exploited

What happened. Deserialization of untrusted data in Puppet's report-processing code (CWE-502, CWE-94). Affected Puppet Enterprise releases: 2023.8.0 to before 2023.8.13, 2025.0.0 to before 2025.12.1 and 2026.0.0 to before 2026.0.1. Perforce's Puppet Core 8.22.2 and 9.1.3 release notes list the fix. The OpenVox advisory lists Server 9.1.0/8.17.0 and Agent 9.2.0/8.31.1 and earlier as affected.

Impact. Code execution on the Puppet Server as its service user, which can reach every managed node. CISA lists it as known exploited (added 17 November 2026; ransomware use "Unknown"). No public source describes the attacks or victims.

Sources: CVE record · Perforce advisory · Puppet Core 8.22.2 · Puppet Core 9.1.3 · CISA KEV

Nov 2026Not a breachProduct vulnerability

CVE-2026-115732: certificate-name authorization bypass in Puppet Server

What happened. Incorrect authorization in the certificate-name matching of trapperkeeper-authorization: a certificate whose name extends or shortens an authorized hostname can be authorized as that host. Fixed in the same releases (CVSS v4.0 9.0).

Impact. Impersonation of other nodes; in Puppet Enterprise, Perforce says, access to CA administration and remote command execution on managed nodes. Needs a certificate with a colliding name, issued by approval or autosign. Not in KEV as of 19 November 2026.

Sources: CVE record · OpenVox notice

Where the reports disagree

  • KEV date: CISA's catalogue gives a date added of 17 November 2026; the catalogue release that carried it is dated 18 November, so some feeds show 18 November.
  • Exploitation: some secondary sites say the CVE is not in KEV; that was true before 17 November. Reports of a public proof of concept come from secondary outlets; the researcher's write-up publishes technical detail.
  • Affected range for Puppet Core is not stated in the release notes we read; the CVE record lists Puppet Enterprise ranges only.

The pattern across the record

The configuration server is a master key

Code on a Puppet Server can reach every managed node. Treat it like a domain controller: patch it first and restrict who can talk to it.

Autosigning turns "authenticated" into "anyone"

The flaw needs a signed agent certificate, and a CA that autosigns without strong checks will hand one to a stranger.

What it means for Perforce (Puppet) customers — and what to do

If you run Puppet Enterprise, Puppet Core, open source Puppet or OpenVox, the question is your server version and your autosign settings, not whether Perforce was breached.

  1. 1.Patch every Puppet Server

    Puppet Enterprise 2023.8.13, 2025.12.1 or 2026.0.1; Puppet Core 8.22.2 or 9.1.3; OpenVox Server 9.2.0 or 8.18.0 with Agent 9.3.0 or 8.32.0. Open source Puppet gets no upstream fix: migrate.

  2. 2.Tighten autosigning and audit certificates

    Turn off autosign where you can, make policy-based autosigning check a secret, and revoke signed certnames you cannot match to a real node.

    Checklist
  3. 3.Limit access to port 8140

    Allow Puppet Server traffic only from the networks where managed nodes live, never from the internet.

  4. 4.Check KEV and set the deadline

    Federal due date 1 December 2026.

    KEV checker
Take this with you
Incident timeline · What Perforce (Puppet) customers should do · Sources

CISO takeaways

Sources

Company statements and regulator filings first, then reputable reporting. Reviewed 19 November 2026.

  1. 1.Report Deserialization Code Execution (CVE-2026-115731) — Perforce, 3 Nov 2026
  2. 2.CVE-2026-115731 (CNA Perforce) — CVE.org, 3 Nov 2026
  3. 3.CVE-2026-115732 (CNA Perforce) — CVE.org, 3 Nov 2026
  4. 4.Puppet Core 8.22.2 release notes — Perforce, Nov 2026
  5. 5.Puppet Core 9.1.3 release notes — Perforce, Nov 2026
  6. 6.OpenVox Server RCE and client impersonation vulnerabilities — OpenVox (oss-security), 3 Nov 2026
  7. 7.Critical CVE updates — Vox Pupuli, 3 Nov 2026
  8. 8.Pulling the right strings for RCE on a Puppet — Neodyme, 3 Nov 2026
  9. 9.Known Exploited Vulnerabilities catalog — CISA, 17 Nov 2026

Frequently asked questions

Was Perforce hacked?

No breach of Perforce or the OpenVox project is reported. CVE-2026-115731 is a vulnerability in Puppet software, fixed on 3 November 2026.

Which versions fix CVE-2026-115731?

Puppet Enterprise 2023.8.13, 2025.12.1 and 2026.0.1; Puppet Core 8.22.2 and 9.1.3; OpenVox Server 9.2.0 and 8.18.0 and Agent 9.3.0 and 8.32.0.

Is CVE-2026-115731 exploited?

CISA says so: it added the CVE to KEV on 17 November 2026 with a due date of 1 December 2026. No public source describes the attacks.

Is OpenVox affected?

Yes. OpenVox, the community fork of Puppet, says the flaws affect all known OpenVox and Puppet versions and fixed them in Server 9.2.0 and 8.18.0 and Agent 9.3.0 and 8.32.0.

Same sourced, verification-tagged timeline, company by company — compare how peers have fared.

Or see the full Breach Index and how to read it.

Independent analysis for security-leadership education; not affiliated with or endorsed by Perforce (Puppet). Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.