Quick answers
- Is CVE-2026-35175 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35175 being exploited in the wild.
- How severe is CVE-2026-35175?
- Medium severity, with a CVSS score of 6.5, published 6 April 2026.
- Which products and versions are affected?
- Ajenti < 2.2.15; ajenti-panel (PyPI) ECOSYSTEM:introduced=0,fixed=2.2.15.
- Is there a fix for CVE-2026-35175?
- Yes. ajenti-panel (PyPI): upgrade to 2.2.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35175 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-35175?
- Check whether you run Ajenti or ajenti-panel (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ajenti-panel (PyPI): upgrade to 2.2.15 or later
pip install "ajenti-panel>=2.2.15"
Technical details
A missing authorization vulnerability (CWE-862) exists in Ajenti's task handling logic. When the 'auth_users' plugin is used for authentication, the system fails to properly verify if a user has superuser privileges before allowing the installation of custom packages. An authenticated attacker with low privileges can exploit this over the network to install arbitrary packages on the host system. This bypasses intended role-based access controls. The issue is addressed in version 2.2.15 by implementing stricter checks on tasks.
Affected products
- Ajenti Ajenti < 2.2.15
Identifiers
- CVE-2026-35175
- GHSA-73jv-44c3-j5p2
- PYSEC-2026-2339
Timeline
- 2026-03-31: patched: Version 2.2.15 released
- 2026-04-01: advisory: GitHub Security Advisory published
- 2026-04-06: disclosed: CVE published to NVD