TL;DR(繁體中文)
美國 CISA 已將 Perforce Puppet Enterprise 的漏洞 CVE-2026-115731 列入「已知被利用漏洞」(KEV)清單——重點不是它的 CVSS 9.4 評分,而是被列入 KEV 代表該漏洞已有實際被利用的證據。漏洞專門影響 Puppet Server,可讓攻擊者執行程式碼;Puppet Server 保存著整個機群的策略、設定與憑證,一旦被攻陷即可向下游推送惡意設定,影響範圍遠超單一主機。每條 KEV 記錄都會附上 BOD 22-01 所要求的個別修補到期日,該日期(而非列入清單的日期)才是營運人員應對齊的時點。注意:BOD 22-01 的修補期限只對美國聯邦民事行政機構具約束力,香港機構除非與美國業務或合規要求掛鈎,否則不受其直接約束,但仍應把該期限視為業界參考基準。
The U.S. Cybersecurity and Infrastructure Security Agency has added a Perforce Puppet Enterprise vulnerability to its Known Exploited Vulnerabilities catalog — a designation that marks it as already exploited in the wild, not merely theoretical. Security Affairs reported the addition on 18 November.
The flaw, CVE-2026-115731, carries a CVSS score of 9.4 and affects Puppet Server, where it could let an attacker execute code. Those numbers matter, but they are not the story. A 9.4 is common enough; membership of the KEV catalog is not. CISA curates that list specifically for vulnerabilities with credible evidence of active exploitation, separating them from the far larger pool of critical flaws that are severe on paper only.
Why this list matters more than the score
Puppet Server sits at the centre of configuration management for many enterprise estates. It holds the policies, manifests and credentials that tell thousands of nodes how to build and maintain themselves — which means a compromised Puppet Server is less a single-host breach than a lever on the entire managed fleet. An attacker who can execute code there gains a privileged staging point from which to push malicious configuration downstream, effectively turning the organisation's own automation tooling against it.
That blast radius is why a KEV listing for this class of bug deserves attention well beyond patch-management teams. The vulnerability affects Puppet Server specifically, and remediation should follow the fixed version released by the vendor, not workarounds.
What operators should do
Start with inventory: identify every Puppet Server instance you run, then confirm each against the vendor's published fixed release. Work to the remediation due date attached to the KEV entry — each record CISA publishes carries its own BOD 22-01 deadline, and it is that date, not the listing date, that operators should plan against.
BOD 22-01 binds U.S. federal civilian executive branch agencies only. It does not directly obligate Hong Kong organisations, public or private, absent a separate U.S. regulatory, contractual or supply-chain linkage — for example, work performed for U.S. federal customers or alignment with U.S. security requirements. Organisations without such ties should treat the KEV deadline as an externally validated benchmark rather than a legal requirement, but the underlying risk calculus does not change: a critical, actively exploited flaw in configuration-management infrastructure warrants prompt patching on its own merits.
The wider picture
Perforce, the U.S.-based software vendor, acquired Puppet in 2022, folding the infrastructure-as-code platform into its broader portfolio of developer and operations tooling. Puppet remains widely used for declarative server configuration across large, heterogeneous environments, making vulnerabilities in its server component a recurring concern for security teams.
The pattern behind this listing is a familiar one: critical infrastructure software accumulates privileges by design, and when flaws in that layer are both severe and demonstrably exploited, they become priority items. Among the many announcements competing for an operator's attention, CISA's KEV catalog remains the clearest public signal of which flaws are past the theoretical stage.
Whatever your organisation's regulatory position, verify your Puppet Server instances against the vendor's fixed release without delay.
TL;DR(繁體中文)
美國 CISA 已將 Perforce Puppet Enterprise 的漏洞 CVE-2026-115731 列入「已知被利用漏洞」(KEV)清單——重點不是它的 CVSS 9.4 評分,而是被列入 KEV 代表該漏洞已有實際被利用的證據。漏洞專門影響 Puppet Server,可讓攻擊者執行程式碼;Puppet Server 保存著整個機群的策略、設定與憑證,一旦被攻陷即可向下游推送惡意設定,影響範圍遠超單一主機。每條 KEV 記錄都會附上 BOD 22-01 所要求的個別修補到期日,該日期(而非列入清單的日期)才是營運人員應對齊的時點。注意:BOD 22-01 的修補期限只對美國聯邦民事行政機構具約束力,香港機構除非與美國業務或合規要求掛鈎,否則不受其直接約束,但仍應把該期限視為業界參考基準。
美國網絡安全及基礎設施安全局(CISA)已將一項 Perforce Puppet Enterprise 漏洞列入其「已知被利用漏洞」(Known Exploited Vulnerabilities,KEV)目錄——該分類代表漏洞已在現實環境中被利用,而非僅屬理論上的風險。Security Affairs 於 11 月 18 日報道此事。
該漏洞編號為 CVE-2026-115731,CVSS 評分達 9.4,影響 Puppet Server,可讓攻擊者執行程式碼。這些數字固然重要,但並非故事的重點。9.4 分的漏洞可謂屢見不鮮,能列入 KEV 目錄卻絕非等閒。CISA 編纂該清單的唯一準則,是漏洞須有可信證據顯示正被積極利用,從而將其與大量僅在紙面上屬「嚴重」的關鍵漏洞區分開來。
為何這份清單比評分更重要
Puppet Server 是眾多企業 IT 環境配置管理的核心,保存著策略(policy)、manifest 及憑證,指示數以千計的節點如何建置及維持自身運作——換言之,一台被入侵的 Puppet Server,其意義不單是一台主機被攻陷,而是控制整個受管機群的槓桿。攻擊者若能在該處執行程式碼,便取得一個高權限的部署據點,藉此向下游推送惡意配置,實質上令組織自身的自動化工具反過來對付自己。
正因波及範圍如此廣泛,這類漏洞登上 KEV 清單一事,值得修補管理團隊以外的各方高度關注。漏洞專門影響 Puppet Server,修補工作應依循供應商發布的修復版本,而非採用權宜繞道方案。
營運人員應採取的措施
首先是盤點:確認你所運行的每一個 Puppet Server 實例,再逐一對照供應商公布的修復版本。並以 KEV 記錄所附的修補到期日為工作目標——CISA 發布的每條記錄均載有各自的 BOD 22-01 期限,營運人員應據以規劃的是該到期日,而非漏洞被列入清單的日期。
BOD 22-01 只對美國聯邦民事行政分支機構具約束力,並不直接約束香港的公營或私營機構,除非該機構另與美國的監管、合約或供應鏈有所掛鈎——例如為美國聯邦客戶提供服務,或須配合美國的安全要求。沒有此類關聯的機構,應將 KEV 期限視為經外部驗證的參考基準,而非法定要求;但底層的風險評估並不因此改變:配置管理基礎設施中一項正在被積極利用的關鍵漏洞,其本身已構成盡快修補的充分理由。
更宏觀的圖像
Perforce 是美國的軟件供應商,於 2022 年收購 Puppet,將此 infrastructure-as-code 平台納入其涵蓋開發者及系統維運工具的產品組合。Puppet 至今仍廣泛用於大型、異質環境中的聲明式伺服器配置,其伺服器組件的漏洞因而一直是安全團隊的反覆憂慮。
這次列入清單背後的模式並不陌生:關鍵基礎設施軟件按設計不斷累積權限,當該層級的漏洞既嚴重又確鑿地被人利用時,便會成為優先處理事項。在眾多爭奪營運人員注意力的消息之中,CISA 的 KEV 目錄始終是公開訊號中最清晰的一個,標示哪些漏洞已超越理論階段。
無論貴機構的監管處境為何,都應即時對照供應商的修復版本,核查你的 Puppet Server 實例。
