External risk intelligence

JumpServer Ansible Automation RCE via Template Injection.

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-104126

JumpServer is an enterprise bastion host and remote access gateway designed to be internet-facing or positioned at the network edge to facilitate secure administrative access. While this specific vulnerability requires authenticated user access to trigger, the product's primary purpose as an externally reachable management portal places it in a category of systems commonly exposed to the public internet.

Code Injection

Fit2cloud Jumpserver

before 4.10.17

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability exists in JumpServer, an open-source system for managing secure access and auditing operations. This issue allows authenticated users with specific permissions to potentially disclose sensitive files or environment variables, and in some cases, execute limited commands. While it does not grant unauthenticated access, it impacts a system designed for secure administrative access.

  • Sensitive information can be exposed.
  • Affects a critical system for secure access.
  • Confirm relevance and ensure systems are updated.

Attack Path

How an attacker could exploit the issue

An attacker with limited privileges can leverage JumpServer's automation task feature to execute crafted Ansible expressions. These expressions can trick the system into disclosing sensitive file or environment information, and in some cases, may allow for limited command execution within the automation process. This vulnerability does not grant unauthenticated access or affect unrelated JumpServer assets.

  • Authenticated user with task creation rights.
  • Crafting automation tasks with lookup behavior.
  • Information disclosure and limited command execution.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, users with permission to create or execute automation tasks in JumpServer could leverage crafted content to trigger sensitive Ansible lookup behaviors. This may lead to the disclosure of files or environment values, and potentially limited command execution within the automation process's privileges. The issue does not provide unauthenticated access or direct access to unrelated JumpServer assets.

  • System files or environment variables at risk.
  • Crafted automation tasks invoke lookups.
  • Disclosure of sensitive information.

Operational Fix

Recommended remediation, mitigation, and detection steps

The JumpServer platform team likely owns this vulnerability due to its role in managing automation tasks. The first practical step is to identify all JumpServer instances, confirm their exposure and business criticality, and then assign an accountable owner for remediation planning.

  • Platform team owns the vulnerability.
  • Verify JumpServer instances and reachability.
  • Plan and coordinate patching with vendor.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is JumpServer?

JumpServer is an open-source bastion host and security audit system. It functions as a centralized gateway that organizations use to manage, monitor, and secure administrative access to their internal servers and network infrastructure, often acting as a bridge between users and critical systems.

What does CVE-2026-104126 mean for security?

This vulnerability is classified as CWE-94, or Improper Control of Generation of Code. In JumpServer, it means the system incorrectly processes user-provided input within its Ansible automation engine. An attacker can inject specific template expressions that trick the engine into executing unauthorized actions, such as reading system files or running limited commands.

How can an attacker trigger this vulnerability?

An attacker must already have legitimate account access with permissions to create or run automation tasks. They trigger the issue by submitting crafted content designed to invoke sensitive Ansible lookup functions. It is important to note that this bug cannot be triggered by unauthenticated users or those without specific task-management privileges.

Is my JumpServer instance at risk?

According to Halo Surface Signal, JumpServer is typically deployed as an internet-facing or edge-positioned gateway to facilitate remote administrative access. Because of this intended design, any instance reachable from the public internet increases the relevance of this vulnerability, even though it requires an authenticated user to initiate the attack.

How do I secure my environment against this?

The primary response is to update your JumpServer installation to version 4.10.17-lts or newer, where this flaw is fixed. Before patching, identify all running instances to assess their reachability and prioritize those exposed to the internet. Coordinate with your platform team to ensure the update is applied according to your organization's maintenance schedule.

References