Vulnerability in ajenti-panel (CVE-2026-35175)
Summary
Vulnerability in ajenti-panel (CVE-2026-35175). Data can be tampered with by attackers. Exploitable via auth_users. Mitigation: upgrade to 2.2.15 or later.
Original description
The description as published by the source.
Ajenti is a Linux and BSD modular server admin panel. Prior to 2.2.15, an authenticated user (using the auth_users plugin authentication method) could install a custom package even if this user is not superuser. This vulnerability is fixed in 2.2.15.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-35175 has been found in ajenti-panel.
Attackers can target a specific entry point like auth_users over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade ajenti-panel to 2.2.15 or later.
If unsure, ask your IT team or search "ajenti-panel CVE-2026-35175" on the vendor's site.
CVE-2026-35175 (ajenti-panel) — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: auth_users
Patched: 2.2.15 — apply immediately
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.
A vulnerability (CWE-862) exists in ajenti-panel. Attackers reach the vulnerable code path via auth_users.
Check the vendor advisory for the affected versions of ajenti-panel. Attack surface: auth_users.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 2.2.15.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ajenti-panel' . 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 'ajenti-panel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ajenti-panelを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ajenti-panel to 2.2.15ステージング環境で 2.2.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com