```
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) moved a critical remote code execution flaw in Perforce Puppet onto its Known Exploited Vulnerabilities (KEV) catalog on Tuesday, 17 November, pointing to reports that attackers are already exploiting it in the wild.
The vulnerability, CVE-2026-115731, carries a CVSS score of 9.4 and affects Puppet Enterprise — the configuration management and infrastructure-as-code platform organisations use to declare, automate and enforce state across large server fleets. Operators should reconcile every installed instance against Perforce's security advisory, which lists the affected Puppet Enterprise releases and the patched releases to upgrade to.
KEV placement is the signal that matters. Inclusion reflects credible reporting of real-world exploitation rather than a theoretical proof-of-concept, which makes CVE-2026-115731 an immediate-patch item instead of one that can wait for a routine maintenance window.
Why a control-plane flaw matters more than its CVSS score suggests
Puppet occupies a structurally privileged position in the environments it manages. Agents on managed nodes authenticate to the control plane using certificates issued by the Puppet infrastructure, and the server routinely handles privileged credentials needed to converge configuration across endpoints. That architecture is precisely what widens the blast radius: an attacker who achieves code execution on the Puppet server is not confined to that host.
From the control plane, attacker-controlled configuration can be pushed to every managed node in the fleet, while the certificate-based trust relationship means agents will act on instructions they believe are legitimate. In effect, a tool built to guarantee compliance and reproducibility becomes the pivot for a configuration-management supply chain compromise — turning a single-server bug into a fleet-wide incident. That is the core reason infrastructure and platform teams should treat this differently from an ordinary high-severity CVE.
The remediation clock
Under CISA's Binding Operational Directive 22-01, federal civilian executive branch agencies must remediate KEV-listed vulnerabilities within 21 days of catalog inclusion. Catalogued on 17 November 2026 — a Tuesday — that 21-day clock places the deadline for CVE-2026-115731 at 8 December 2026.
Scope deserves precision: BOD 22-01 binds U.S. federal civilian agencies only, and private-sector organisations outside that mandate carry no regulatory obligation to hit the date. In practice, though, the KEV deadline functions as a de facto priority queue — a signal from CISA that the flaw is being used against real targets and should be scheduled ahead of lower-risk patch-cycle work.
Action checklist for enterprise operators
- Confirm exposure. Identify every Puppet Enterprise server in the estate, including staging, disaster-recovery and legacy instances that routinely escape inventory.
- Reconcile every instance against Perforce's security advisory. The advisory carries the definitive affected-versus-fixed Puppet Enterprise version list — no instance should be called out of scope without checking it against the vendor's figures.
- Prioritise internet-reachable and broadly scoped servers. Any control plane with a wide node scope or direct exposure should be patched first, followed by an isolation and access-control review of the administrative interface.
- Rotate credentials and audit trust. After patching, review recent catalog changes, node classification and agent certificate activity for signs that configuration was tampered with before the fix landed.
- Treat unpatched systems as targeted. KEV listing means the exploit path is in circulation; unpatched control planes should be assumed to be targets.
```
美國網絡安全及基礎設施安全局(CISA)於 11 月 17 日(星期二)將 Perforce Puppet 的一項嚴重遠端代碼執行(remote code execution)漏洞列入其「已知遭利用漏洞」(Known Exploited Vulnerabilities,KEV)目錄,指出已有報告顯示攻擊者正在現實環境中利用該漏洞。
該漏洞編號為 CVE-2026-115731,CVSS 評分為 9.4,影響 Puppet Enterprise —— 即企業用來宣告、自動化及強制執行大規模伺服器機群設定狀態的設定管理及 infrastructure-as-code 平台。營運人員應將每一個已安裝的實例與 Perforce 安全公告逐一對照核實,該公告列明受影響的 Puppet Enterprise 版本,以及應升級至的已修補版本。
列入 KEV 才是關鍵訊號。收錄意味著有可信報告證實漏洞已在現實中遭利用,而非僅屬理論性的 proof-of-concept,這使 CVE-2026-115731 成為須即時修補的事項,而不能留待例行維護時段處理。
為何控制平面漏洞的影響遠超 CVSS 評分所示
Puppet 在其所管理的環境中佔有結構上特權的位置。受管節點上的 agent 以 Puppet 基礎設施簽發的 certificate 向控制平面進行身份驗證,而伺服器日常亦處理統合各終端設定所需的高權限憑證。正是這項架構擴大了爆炸半徑:攻擊者一旦在 Puppet 伺服器上取得代碼執行權限,影響便不會局限於該主機。
從控制平面出發,攻擊者可控的設定可推送至機群中每一個受管節點,而基於 certificate 的信任關係更意味著 agent 會執行它們認為正當的指令。換言之,一個原本用以保障合規性及可重複性的工具,搖身一變成為設定管理供應鏈遭入侵的支點 —— 將單一伺服器的漏洞轉化為遍及整個機群的事故。這正是基建及平台團隊應將此事與一般高危 CVE 區別對待的核心理由。
修補時限
根據 CISA 的強制性行動指令 22-01(Binding Operational Directive 22-01),聯邦民政行政部門機構須在漏洞列入 KEV 目錄後 21 日內完成修補。漏洞於 2026 年 11 月 17 日(星期二)收錄,該 21 日時限意味著 CVE-2026-115731 的期限為 2026 年 12 月 8 日。
適用範圍須講求精確:BOD 22-01 僅約束美國聯邦民政機構,該指令範圍以外的私營機構並無法規義務須在此期限前完成修補。然而實務上,KEV 期限實際上發揮了事實上的優先處理隊列作用 —— 這是 CISA 傳達漏洞已被用於攻擊真實目標、應排於風險較低的修補周期工作之前處理的訊號。
企業營運人員行動清單
- 確認影響範圍。 清查整個資產組合中的每一部 Puppet Enterprise 伺服器,包括例行避過資產盤點的 staging、災難復原及舊版實例。
- 逐一對照 Perforce 安全公告核實各實例。 公告載明受影響與已修復 Puppet Enterprise 版本的權威清單 —— 任何實例在未對照廠商數據核實之前,均不得宣稱不屬範圍。
- 優先處理可經互聯網存取及範圍廣泛的伺服器。 任何節點範圍寬廣或直接對外暴露的控制平面應先行修補,隨後檢視管理介面的隔離及存取控制。
- 輪換憑證並審核信任關係。 修補後,檢視近期的 catalog 變更、node 分類及 agent certificate 活動,查找設定在修復生效前遭人竄改的跡象。
- 視未修補系統為已遭鎖定目標。 列入 KEV 意味著 exploit 路徑正在流傳;未修補的控制平面應被視為攻擊目標。
