{"id":4400,"date":"2026-11-18T06:32:46","date_gmt":"2026-11-18T14:32:46","guid":{"rendered":"https:\/\/cyber.mag212.com\/puppet-server-cve-2026-115731-report-deserialization-rce-cisa-kev\/"},"modified":"2026-11-18T06:32:46","modified_gmt":"2026-11-18T14:32:46","slug":"puppet-server-cve-2026-115731-report-deserialization-rce-cisa-kev","status":"publish","type":"post","link":"https:\/\/cyber.mag212.com\/fr\/puppet-server-cve-2026-115731-report-deserialization-rce-cisa-kev\/","title":{"rendered":"Puppet Server RCE (CVE-2026-115731) Is Now Exploited: How the Report Deserialization Flaw Works and How to Fix It"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><em>From the <a href=\"https:\/\/cyber.mag212.com\/one-equals-sign-too-many-mag212-cyber-daily-november-18-2026\/\">MAG212 CYBER Daily, 18 November 2026<\/a>. Every command is copied from official documentation or the cited analysis and was <strong>not tested by MAG212<\/strong>; run it only on systems you are authorised to administer.<\/em><\/p>\n\n\n\n<p class=\"m2-status wp-block-paragraph\"><strong>Status:<\/strong> <strong>Actively exploited per CISA<\/strong>, which added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog on 17 November 2026 with a remediation deadline of 1 December for US federal agencies. CISA lists ransomware use as unknown. Perforce, Vox Pupuli and researchers at Neodyme disclosed the flaw with fixes on 3 November; a working proof-of-concept is included in the OpenVox advisory. Severity: CVSS 4.0 score 9.4. <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-2\">[2]<\/a><\/sup><sup><a href=\"#src-4\">[4]<\/a><\/sup><sup><a href=\"#src-5\">[5]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What happened<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">CVE-2026-115731 is a deserialization flaw in the report-processing code of Puppet Server, used by Puppet Enterprise, Puppet Core and the open-source fork OpenVox. Perforce describes it as allowing a client that holds any CA-signed agent certificate to execute arbitrary code on the Puppet Server with the permissions of its service account. SecurityWeek reports the flaw was flagged as exploited on 4 November, before CISA&#8217;s listing. <sup><a href=\"#src-2\">[2]<\/a><\/sup><sup><a href=\"#src-5\">[5]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Who is affected<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Product<\/th><th>Fixed in<\/th><\/tr><\/thead><tbody><tr><td>Puppet Enterprise<\/td><td>2023.8.13, 2025.12.1, 2026.0.1<\/td><\/tr><tr><td>Puppet Core<\/td><td>9.1.3, 8.22.2<\/td><\/tr><tr><td>OpenVox Server and OpenVoxDB<\/td><td>9.2.0 or 8.18.0<\/td><\/tr><tr><td>OpenVox Agent<\/td><td>9.3.0 or 8.32.0<\/td><\/tr><tr><td>Open Source Puppet<\/td><td>no further updates; migrate<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Fixed versions as reported by SecurityOnline and SecurityWeek from the vendor and OpenVox advisories. Check the Perforce advisory before upgrading. <sup><a href=\"#src-2\">[2]<\/a><\/sup><sup><a href=\"#src-4\">[4]<\/a><\/sup><sup><a href=\"#src-5\">[5]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why this matters<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A Puppet server decides what runs on every machine it manages. Code execution on it exposes the certificate authority&#x27;s signing key, which means an attacker can impersonate any node and, through the configurations it serves, potentially reach the whole fleet. A public exploit has existed since disclosure, so exploitation was a matter of time. <em>(MAG212 analysis)<\/em><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/puppet-18nov-diagram.png\"><img decoding=\"async\" src=\"https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/puppet-18nov-diagram.png\" alt=\"Puppet Server RCE is now exploited. Diagram by MAG212 CYBER.\"\/><\/a><figcaption class=\"wp-element-caption\">Diagram: MAG212 CYBER. Solid red = observed or confirmed; dashed amber = reported or unverified; green = recommended control.<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">How the attack works<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>A certificate:<\/strong> the attacker needs a CA-signed agent certificate. Any enrolled node has one. If the CA uses na\u00efve autosigning, an outsider can simply request one, which turns this into an effectively unauthenticated attack chain. <sup><a href=\"#src-4\">[4]<\/a><\/sup><sup><a href=\"#src-6\">[6]<\/a><\/sup><\/li>\n\n<li><strong>A crafted report:<\/strong> after each run, agents send a JSON report to the server. An event inside that report can carry a serialized Ruby object. <sup><a href=\"#src-4\">[4]<\/a><\/sup><\/li>\n\n<li><strong>Deserialization:<\/strong> the server trusts an attacker-supplied type name, which eventually reaches a Ruby <code>class_eval<\/code> call, so a malicious event object runs code on the server. <sup><a href=\"#src-4\">[4]<\/a><\/sup><\/li>\n\n<li><strong>Impact:<\/strong> code runs as the Puppet service user. That gives access to the CA signing key, which Red Hat notes enables further compromise of managed systems. <sup><a href=\"#src-3\">[3]<\/a><\/sup><sup><a href=\"#src-4\">[4]<\/a><\/sup><\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">A companion flaw, CVE-2026-115732 (CVSS 9.0), was fixed in the same releases. The trapperkeeper-authorization library treated plain hostname rules like wildcards, so a certificate for a subdomain could impersonate its parent host; Perforce says this can lead to remote command execution on managed nodes in Puppet Enterprise. One outlet reports it is also being exploited; MAG212 could not confirm that. <sup><a href=\"#src-4\">[4]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What defenders should look for<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Certificates you do not recognise in the CA&#8217;s signed or pending list.<\/li>\n\n<li>Report submissions (<code>PUT \/puppet\/v3\/report<\/code>) from unexpected hosts or at unusual times. <sup><a href=\"#src-3\">[3]<\/a><\/sup><\/li>\n\n<li>New processes, files or outbound connections started by the Puppet service user on the server.<\/li>\n\n<li>Changes to the CA directory or unexpected access to the CA private key.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">How to investigate<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These commands are <strong>read-only<\/strong>, run on the Puppet CA server, and come from Puppet&#8217;s documentation and the puppetserver-ca manual. <strong>Not tested by MAG212.<\/strong> <sup><a href=\"#src-6\">[6]<\/a><\/sup><sup><a href=\"#src-7\">[7]<\/a><\/sup><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>puppet config print autosign --section server\npuppetserver ca list --all<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The first shows how the CA decides to sign requests: <code>true<\/code> means it signs every request (na\u00efve autosigning); a file path means an allowlist file or a policy executable. The second lists signed and pending certificates so you can spot nodes you do not recognise.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to contain and remediate<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Patch<\/strong> to a fixed version from the table above. Patching is the only full fix. <sup><a href=\"#src-4\">[4]<\/a><\/sup><\/li>\n\n<li><strong>Until you can patch<\/strong>, restrict network access to the Puppet server to the networks that need it, and restrict access to the report endpoint. <sup><a href=\"#src-3\">[3]<\/a><\/sup><sup><a href=\"#src-4\">[4]<\/a><\/sup><\/li>\n\n<li><strong>Disable or tighten autosigning:<\/strong> set <code>autosign = false<\/code> in the <code>[server]<\/code> section of the CA&#8217;s puppet.conf, or use a verified policy executable. <sup><a href=\"#src-6\">[6]<\/a><\/sup><\/li>\n\n<li><strong>After upgrading<\/strong>, review custom auth.conf rules. <sup><a href=\"#src-4\">[4]<\/a><\/sup><\/li>\n\n<li><strong>If compromise is suspected<\/strong>, treat the CA as exposed: preserve evidence, then plan to regenerate the CA and re-issue agent certificates, and review the code and data the server distributed during the exposure.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">How to verify recovery<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The server reports a fixed version after restart.<\/li>\n\n<li><code>puppet config print autosign --section server<\/code> no longer returns <code>true<\/code>.<\/li>\n\n<li>The certificate list contains only nodes you expect.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Prevention and awareness<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>For administrators:<\/strong> configuration-management servers are tier-zero systems. Keep them off general networks and patch them on the same timeline as domain controllers.<\/li>\n\n<li><strong>For decision-makers:<\/strong> Open Source Puppet receives no further updates; budget a migration to a supported line or to OpenVox.<\/li>\n\n<li><strong>For security teams:<\/strong> alert on new certificate signings and on new processes spawned by the Puppet service account.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Related on MAG212 CYBER<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/cyber.mag212.com\/one-equals-sign-too-many-mag212-cyber-daily-november-18-2026\/\">MAG212 CYBER Daily, 18 November 2026: One equals sign too many<\/a> (full issue and PDF)<\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/keys-outlived-the-job-mag212-cyber-daily-november-17-2026\/\">MAG212 CYBER Daily, 17 November 2026: Keys that outlived the job<\/a><\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/boxes-nobody-patches-mag212-cyber-daily-november-16-2026\/\">MAG212 CYBER Daily, 16 November 2026: The boxes nobody patches<\/a><\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/the-keys-were-already-inside-mag212-cyber-weekly-november-14-2026\/\">MAG212 CYBER Weekly, 14 November 2026<\/a><\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/subscribe-free\/\">Subscribe free to MAG212 CYBER<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Sources<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><span id=\"src-1\">[1]<\/span> CISA, &#8220;<a href=\"https:\/\/www.cisa.gov\/news-events\/alerts\/2026\/11\/17\/cisa-adds-one-known-exploited-vulnerability-catalog\" rel=\"noopener\" target=\"_blank\">CISA adds one known exploited vulnerability to catalog<\/a>&#8220;, 17 Nov 2026.<\/li>\n\n<li><span id=\"src-2\">[2]<\/span> Perforce, &#8220;<a href=\"https:\/\/portal.perforce.com\/s\/cve\/a91Qi000003IaHpIAK\/report-deserialization-code-execution\" rel=\"noopener\" target=\"_blank\">CVE-2026-115731: report deserialization code execution<\/a>&#8220;, 3 Nov 2026.<\/li>\n\n<li><span id=\"src-3\">[3]<\/span> Red Hat, &#8220;<a href=\"https:\/\/access.redhat.com\/security\/cve\/CVE-2026-115731\" rel=\"noopener\" target=\"_blank\">CVE-2026-115731 description and mitigation<\/a>&#8220;, Nov 2026.<\/li>\n\n<li><span id=\"src-4\">[4]<\/span> SecurityOnline, &#8220;<a href=\"https:\/\/securityonline.info\/puppet-server-rce-cve-2026-115731-poc\/\" rel=\"noopener\" target=\"_blank\">Puppet Server RCE CVE-2026-115731: public PoC<\/a>&#8220;, Nov 2026.<\/li>\n\n<li><span id=\"src-5\">[5]<\/span> SecurityWeek, &#8220;<a href=\"https:\/\/www.securityweek.com\/critical-perforce-puppet-rce-exploited-in-attacks\/\" rel=\"noopener\" target=\"_blank\">Critical Perforce Puppet RCE exploited in attacks<\/a>&#8220;, 17 Nov 2026.<\/li>\n\n<li><span id=\"src-6\">[6]<\/span> Puppet documentation, &#8220;<a href=\"https:\/\/puppet.com\/docs\/puppet\/7\/ssl_autosign\" rel=\"noopener\" target=\"_blank\">Autosigning certificate requests<\/a>&#8220;, Docs 2026.<\/li>\n\n<li><span id=\"src-7\">[7]<\/span> Ubuntu manpages, &#8220;<a href=\"https:\/\/manpages.ubuntu.com\/manpages\/lunar\/man1\/puppetserver-ca.1.html\" rel=\"noopener\" target=\"_blank\">puppetserver-ca(1): Puppet Server CA management command<\/a>&#8220;, Docs 2026.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Written and edited by El Mostafa Ouchen for MAG212 CYBER. Facts checked against the sources above as of 18 November 2026, 6:00 AM PT.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>CISA added CVE-2026-115731, a report-deserialization flaw in Puppet Server and OpenVox, to its Known Exploited Vulnerabilities catalog on 17 November. Any client with a signed agent certificate can run code on the server and reach the CA signing key. Fixed versions, autosign checks and what to do.<\/p>","protected":false},"author":1,"featured_media":4391,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,15],"tags":[62,454,453,455,452,442,417],"class_list":["post-4400","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-critical-cves","category-threat-intelligence","tag-cisa-kev","tag-configuration-management","tag-cve-2026-115731","tag-deserialization","tag-openvox","tag-puppet","tag-vulnerability-management"],"_links":{"self":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4400","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/comments?post=4400"}],"version-history":[{"count":0,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4400\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/media\/4391"}],"wp:attachment":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/media?parent=4400"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/categories?post=4400"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/tags?post=4400"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}