A newly disclosed Java vulnerability, dubbed Java4Shell and tracked as CVE-2026-114938, lets attackers with no account run their own code on Jira, Jenkins, Keycloak and three further widely deployed applications — but only on servers running Java 17.0.6 or later on x86-64 Intel or AMD processors that support the AVX-512 VBMI instruction set.
The flaw was disclosed this week by security research firm Calif and covered by The Hacker News on 18 November.
The hardware precondition is the detail that matters most for administrators. The vulnerable code path only executes on chips exposing AVX-512 VBMI, so an estate that fails that check is not exposed to this particular bug — and an estate that passes it needs to treat the issue as urgent regardless of which application is in front of the JVM.
It is worth noting that AVX-512 VBMI is far from exotic: the flag is common on recent server-class Intel parts (Ice Lake Xeon and later) and AMD parts (Zen 4 / EPYC Genoa and later). "Our CPUs are modern" is therefore not the same as "we're safe" — the flag check below still has to be run.
Jira, Jenkins and Keycloak are staples of in-house developer and ops stacks, so this story is broadly relevant to IT teams anywhere running internal instances of these tools.
Are you affected? A five-step triage
1. Check the CPU flags, not the CPU model. Query the hypervisor-exposed flags inside the guest (grep -o 'avx512_vbmi' /proc/cpuinfo on Linux) rather than trusting a datasheet or the physical host's specification. In heavily virtualised estates, a host may support AVX-512 VBMI while guests do not — or the reverse exposure may be masked. A "not vulnerable" verdict reached from the wrong layer is a likely false negative, so record how the conclusion was reached; it will need re-testing whenever a workload is migrated.
2. Inventory every JDK in the estate. Calif's advisory places the vulnerable code in Java 17.0.6 and later. That inventory must extend beyond bare-metal installs to container images, CI runners and sidecars — any place a JVM is bundled and nobody is explicitly tracking it.
3. Understand who owns the fix. Because the flaw sits in the Java runtime rather than in application code, Jira, Jenkins, Keycloak and three further affected applications inherit the exposure from the JVM beneath them. The defective code ships with the JDK, so neither a JDK bump nor an application upgrade can be assumed sufficient on its own: the fix is split across the runtime layer and the application layer, and teams must confirm per-vendor fix status against the primary advisory before declaring remediation complete. Platform teams that do not own the affected applications still need to be in the loop.
4. Gate anonymous access as a compensating control. Where immediate upgrading is not feasible, restrict unauthenticated entry points to the affected services behind an authenticated reverse proxy or VPN, and watch for exploit attempts in access logs.
5. Close the JVM inventory blind spot. Most patch programmes track application versions but not the JVM beneath them. Treat Java runtime versions as a standard inventory item going forward, so the next runtime-level flaw does not require a manual hunt through the estate.
Why this matters
Most application vulnerabilities are fixed inside a given project's own codebase, on that project's release cadence. Java4Shell is a runtime-level flaw: the defective code ships with the JDK, and application teams cannot resolve it in their own source. That makes the JVM part of the standard dependency inventory — a blind spot in many organisations.
The reachability of the issue across Jira, Jenkins and Keycloak — three of the most common internal developer and IT service tools — means a single vulnerable JDK image can propagate widely through an estate before anyone notices. The virtualisation wrinkle on the hardware gate complicates matters further: risk-scoring tools that read host specifications rather than guest-visible flags can mark an estate clean when it is not.
Note on sourcing: The CVSS score, the complete list of the six affected applications, per-vendor patch versions and any confirmed workaround short of patching were not available in the material reviewed for this article and are deliberately omitted rather than estimated. Administrators should confirm the CVE identifier, the Java version floor and mitigation guidance against Calif's primary advisory before acting.
一項新披露的 Java 漏洞,代號 Java4Shell,編號為 CVE-2026-114938,允許攻擊者在無需任何帳戶的情況下,在 Jira、Jenkins、Keycloak 及另外三款廣泛部署的應用程式上執行自行撰寫的程式碼 — 但前提是伺服器須運行 Java 17.0.6 或更新版本,並且搭載支援 AVX-512 VBMI 指令集的 x86-64 Intel 或 AMD 處理器。
該缺陷由安全研究公司 Calif 於本週披露,並由 The Hacker News 於 11 月 18 日報道。
硬件前提條件是管理員最需要關注的細節。受漏洞影響的程式碼路徑只會在支援 AVX-512 VBMI 的晶片上執行,因此不符合此項檢查的系統並不受此特定缺陷影響;而通過此項檢查的系統,則無論 JVM 前端運行的是哪款應用程式,都必須將此問題視為緊急事項處理。
值得留意的是,AVX-512 VBMI 並非罕見功能:該指令集標記常見於近期的伺服器級 Intel 處理器(Ice Lake Xeon 及其後型號)以及 AMD 處理器(Zen 4 / EPYC Genoa 及其後型號)。因此,「我們的 CPU 是新款的」並不等同於「我們是安全的」 — 以下的指令集檢查仍必須執行。
Jira、Jenkins 和 Keycloak 是企業內部開發及 Ops 技術架構的常見組成部分,因此本文對各地運行這些工具內部實例的 IT 團隊均有廣泛參考價值。
你是否受影響?五步分診流程
1. 檢查 CPU 指令集標記,而非 CPU 型號。 應查詢虛機內部由 hypervisor 暴露的指令集標記(在 Linux 上執行 grep -o 'avx512_vbmi' /proc/cpuinfo),而非依賴規格表或實體主機的規格。在高度虛擬化的環境中,主機可能支援 AVX-512 VBMI 而虛機不支援 — 或相反的暴露情況可能被掩蓋。在錯誤層級得出的「不受影響」結論很可能屬假陰性,因此必須記錄該結論的得出方式;每逢工作負載遷移時,均需重新測試。
2. 盤點環境中的每一個 JDK。 Calif 的安全公告將受漏洞影響的程式碼定位於 Java 17.0.6 及其後版本。此項盤點必須涵蓋裸機安裝以外的範圍,包括 container image、CI runner 及 sidecar — 即任何捆綁了 JVM 而沒有人明確追蹤的地方。
3. 理解由誰負責修復。 由於缺陷位於 Java runtime 而非應用程式程式碼,Jira、Jenkins、Keycloak 及另外三款受影響的應用程式均從其下方的 JVM 繼承此暴露風險。有缺陷的程式碼隨 JDK 一併發佈,因此不能假設單靠升級 JDK 或升級應用程式便已足夠:修復工作橫跨 runtime 層及應用程式層,團隊必須對照主要安全公告逐一確認各供應商的修復狀態,方可宣布補救工作完成。即使平台團隊並不擁有受影響的應用程式,仍須知悉此事。
4. 以匿名訪問限制作為補償性控制措施。 在無法立即升級的情況下,應透過通過認證的 reverse proxy 或 VPN 將受影響服務的無需認證入口封鎖,並密切監察存取日誌中的漏洞利用嘗試。
5. 填補 JVM 盤點的盲點。 大部分修補計劃只追蹤應用程式版本,卻忽略其下方的 JVM。往後應將 Java runtime 版本列為標準盤點項目,使下一項 runtime 層面的缺陷無需再對整個環境進行人手搜尋。
為何此事重要
大多數應用程式漏洞均在特定專案自身的 codebase 內修復,並依循該專案的發佈節奏。Java4Shell 屬 runtime 層面的缺陷:有缺陷的程式碼隨 JDK 一併發佈,應用程式團隊無法在自身源碼中解決。這使 JVM 成為標準依賴項盤點的一部分 — 而這正是許多機構的盲點。
該問題可觸及 Jira、Jenkins 和 Keycloak — 三款最常見的內部開發及 IT 服務工具 — 意味著單一受漏洞影響的 JDK image 可在無人察覺的情況下在整個環境中廣泛傳播。硬件閘門上的虛擬化因素令情況更為複雜:只讀取主機規格而非虛機可見標記的風險評分工具,可能會將實際並非安全的環境標記為合規。
資料來源說明: CVSS 評分、六款受影響應用程式的完整清單、各供應商的修補版本,以及任何已確認而毋須安裝補丁的緩解方案,均未見於本文審閱的素材中,因此刻意略去而不作估算。管理員在採取行動前,應對照 Calif 的主要安全公告核實 CVE 編號、Java 版本下限及緩解指引。
