The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added vulnerabilities affecting four distinct software stacks to its Known Exploited Vulnerabilities (KEV) catalogue, according to Security Affairs: flaws in Synology DSM, BerriAI LiteLLM, Vanderbilt REDCap, and Apache Axis.

The listing matters because inclusion in the KEV catalogue is not a routine housekeeping exercise. CISA only adds a vulnerability once it has reliable evidence of active exploitation in the wild. For administrators, that converts an abstract CVE into a live operational question: is this software on my network, and has it already been reached?

Where administrators should look first

The two additions with the broadest day-to-day impact are Synology DSM and LiteLLM.

Synology's DiskStation Manager underpins a large installed base of network-attached storage appliances in small offices, home labs, and enterprise branch deployments alike. NAS boxes are attractive targets precisely because they sit at the intersection of valuable data and often-lax patch cadence; they are frequently exposed directly to the internet for remote access. Any DSM flaw with evidence of exploitation should trigger an immediate review of firmware level, remote-access configuration, and — critically — whether default or weak credentials remain in place.

LiteLLM, the open-source gateway layer used to route and manage requests across large language model APIs, represents a newer class of exposure. As organisations increasingly place an AI gateway at the front of their model infrastructure, that gateway becomes a single point of failure: it typically holds API keys, sits on internal networks with wide reach, and is often exposed to developer tooling or external traffic. A vulnerability being actively exploited in this layer is a reminder that AI infrastructure inherits the same patching discipline as any other internet-facing service — and that this layer is currently being treated as a lower-priority component than it deserves.

The long tail: research tooling and legacy middleware

Vanderbilt REDCap — the research data-capture platform widely used in academic and clinical research — occupies a specialised niche. Installations are often managed by individual research groups rather than central IT, which means they are prone to lingering unpatched instances holding sensitive study data.

Apache Axis 1.x is the harder case. The SOAP toolkit has long been out of active development, and for many estates there is no practical upgrade path — organisations are left with compensating controls: removing the component, isolating it behind strict network rules, or filtering the specific request patterns the flaw depends on. Where a vulnerable Axis deployment cannot be patched, isolation is not optional.

What the listing actually obliges

CISA's Binding Operational Directive 22-01 establishes the remediation clock for federal civilian executive branch agencies: KEV-listed vulnerabilities must generally be patched within two weeks of the due date CISA assigns, with the exact mechanics set out on the directive's own page. Private-sector organisations are not bound by the directive, but the security community has effectively adopted the KEV catalogue as a de facto patching benchmark — it is one of the few publicly maintained, evidence-based lists of what is genuinely being attacked right now.

A practical checklist for tonight

  • Inventory Synology NAS devices and confirm current DSM firmware, including any units outside formal asset management.
  • Locate LiteLLM (and comparable AI gateway) deployments; verify version, exposure surface, and key rotation.
  • Audit REDCap instances for upstream availability and patch level, especially departmental installs outside central IT.
  • Identify any Axis 1.x components; where no patch exists, apply isolation and monitoring as a stopgap.
  • Subscribe to CISA's machine-readable KEV feed so new listings surface automatically in your vulnerability-management workflow.

Exact CVE identifiers, severity scores, and per-item remediation due dates for all four additions are published directly in CISA's KEV catalogue, which remains the authoritative source for verification before any patching decisions are made.


據 Security Affairs 報導,美國網絡安全和基礎設施安全局(CISA)已將影響四套不同軟件系統的漏洞加入其已知遭利用漏洞(KEV)目錄,涉及 Synology DSM、BerriAI LiteLLM、Vanderbilt REDCap 及 Apache Axis 的漏洞。

此次收錄意義重大,因為漏洞獲納 KEV 目錄並非例行的清單整理工作。CISA 只會在掌握可靠證據證明漏洞已在現實環境中遭主動利用後,才會將其加入。對系統管理員而言,這會把抽象的 CVE 轉化為切身的營運問題:這款軟件是否在我網絡上,以及它是否已經遭到入侵?

系統管理員應優先檢視的地方

對日常運作影響最廣泛的兩項新增項目,是 Synology DSM 與 LiteLLM。

Synology 的 DiskStation Manager 是大量網絡附加存儲(NAS)設備的基礎,廣泛見於小型辦公室、家庭實驗室及企業分支架構。NAS 設備之所以成為熾手可熱的攻擊目標,正因它處於有價值數據與往往鬆懈的修補節奏的交匯點;這類設備經常直接暴露於互聯網以供遙距存取。任何有遭利用證據的 DSM 漏洞,都應立即觸發對 firmware 版本、遙距存取配置的檢視——以及至關重要的一點:默認或弱密碼憑證是否仍然存在。

LiteLLM 是用於路由及管理大型語言模型 API 請求的開源 gateway 層,代表了一類較新的暴露形式。隨著越來越多機構在模型基礎架構前端設置 AI gateway,該 gateway 便成為單一故障點:它通常持有 API key、坐擁覆蓋範圍廣泛的內部網絡,而且往往對開發者工具或外部流量開放。這一層出現遭主動利用的漏洞,提醒我們 AI 基礎設施須同樣遵守任何其他連接互聯網服務的修補紀律——而目前這一層所獲重視的優先次序,明顯低於其應有的水平。

長尾目標:研究工具與遺留中間件

Vanderbilt REDCap——廣泛應用於學術及臨床研究的數據採集平台——位處專門利基。其安裝往往由個別研究小組而非中央 IT 部門管理,這意味著容易遺留長期未修補、存放敏感研究數據的實例。

Apache Axis 1.x 則是更棘手的情況。這套 SOAP 工具套件早已停止活躍開發,對許多系統而言並無實際升級路徑——機構只能採用補償性控制措施:移除相關組件、以嚴格網絡規則將其隔離,或過濾該漏洞所依賴的特定 request 模式。對於無法修補的 vulnerable Axis 部署,隔離並非可選項。

收錄清單的實際約束

CISA 的具約束力行動指令 22-01 為聯邦民事行政分支機構訂明了修補時限:KEV 列出的漏洞一般須在 CISA 指定的到期日後兩週內完成修補,具體機制則詳載於該指令本身的頁面。私營機構並不受該指令約束,但安全社群實質上已將 KEV 目錄採納為事實上的修補基準——它是少數由公眾維護、以證據為基礎的清單之一,列明當前真正正遭攻擊的目標。

今晚即可執行的實用清單

  • 盤點 Synology NAS 設備,確認現時 DSM firmware 版本,包括所有未納入正式資產管理的機器。
  • 找出 LiteLLM(及同類 AI gateway)部署;核實版本、受攻擊面及 key 輪換情況。
  • 審計 REDCap 實例的上游可用性與修補水平,尤其是脫離中央 IT 管轄的部門自行安裝版本。
  • 識別任何 Axis 1.x 組件;如無修補程式可用,須以隔離及監控作為過渡措施。
  • 訂閱 CISA 的機器可讀 KEV feed,使新增條目自動呈現在漏洞管理工作流程之中。

四項新增漏洞的準確 CVE 編號、嚴重性評分及逐項修補到期日,均直接刊載於 CISA 的 KEV 目錄;在作出任何修補決定之前,該目錄仍是核實資訊的權威來源。

新聞來源 / Original News Source