---
id: "CVE-2026-112159"
kind: "vulnerability"
aliases: ["CVE-2026-112159"]
title: "JumpServer: template rendering flaw lets remote users inject OS commands"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["bastion", "jumpserver", "other", "self-hosted"]
not_affected_if: ["unknown"]
published_at: "2026-10-19T17:17:13+00:00"
first_seen_at: "2026-10-23T21:57:18+00:00"
updated_at: "2026-10-25T03:55:51+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112159", "first_seen_at": "2026-10-23T21:57:18+00:00"}]
---

# JumpServer: template rendering flaw lets remote users inject OS commands

JumpServer up to version 4.10.19 has an OS command injection flaw in its template rendering, where the IP/HOST argument is not sanitized. A remote attacker can run operating system commands on the server, and the exploit has been publicly disclosed.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed JumpServer version and confirm whether it is `4.10.19` or earlier.
- unknown

## Fix

- Upgrade JumpServer to `5.0.0` or later, which the sources say fixes the issue.
- The vendor says a v4 release will also include the fix; the sources do not name that version.
- Patch identifier per sources: `fcf2904cdb884230e9676f50f37a44d09fa97040`.

## Timeline

- 2026-10-23T21:57:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-112159

## From the sources

A security vulnerability has been detected in JumpServer up to 4.10.19. The affected element is an unknown function of the component Template Rendering. The manipulation of the argument IP/HOST leads to os command injection. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. Upgrading to version 5.0.0 is sufficient to fix this issue. The identifier of the patch is fcf2904cdb884230e9676f50f37a44d09fa97040. The affected component should be upgraded. The vendor confirms: "This issue was identified quite some time ago, and we have already fixed it in the v5 branch. (...) The fix will also be included in an upcoming v4 release.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_