Authorization Flaw in JumpServer (CVE-2026-44846)
Summary
Vulnerability in JumpServer (CVE-2026-44846). Confidential information can be exposed externally. Exploitable via POST /api/v1/users/users/invite/.
Original description
The description as published by the source.
JumpServer is an open source bastion host and an operation and maintenance security audit system. Prior to 4.10.17, a user with the users.invite_user permission can submit an existing member to POST /api/v1/users/users/invite/, causing the organization invitation logic in apps/users/api/user.py to execute user.org_roles.set(org_roles) and replace the member's existing organization roles, which can escalate privileges or downgrade administrators. This issue is fixed in version 4.10.17.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44846 has been found in JumpServer.
Attackers can target a specific entry point like POST /api/v1/users/users/invite/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "JumpServer CVE-2026-44846" on the vendor's site.
CVE-2026-44846 (JumpServer) — CWE-863 / CVSS v3 6.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/users/users/invite/
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in JumpServer. Attackers reach the vulnerable code path via POST /api/v1/users/users/invite/.
Check the vendor advisory for the affected versions of JumpServer. Attack surface: POST /api/v1/users/users/invite/.
Severity: Medium (CVSS 6.2/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/v1/users/users/invite/ requests with malformed payloads or SQL meta-characters. Run grep -r 'JumpServer' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'JumpServer' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
JumpServerを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/v1/users/users/invite/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/users/users/invite/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/v1/users/users/invite/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。