Quick answers
- Is CVE-2026-27975 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-27975 being exploited in the wild.
- How severe is CVE-2026-27975?
- Critical severity, with a CVSS score of 9.8, published 27 October 2026.
- Which products and versions are affected?
- Ajenti < 2.2.13; aj (PyPI) < 2.2.13, ECOSYSTEM:introduced=0,fixed=2.2.13.
- Is there a fix for CVE-2026-27975?
- Yes. aj (PyPI): upgrade to 2.2.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-27975 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-27975?
- Check whether you run Ajenti or aj (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
- aj (PyPI): upgrade to 2.2.13 or later
pip install "aj>=2.2.13"
Technical details
An improper access control vulnerability (CWE-284) allows unauthenticated remote code execution via a network attack vector with no preconditions. The vulnerability enables an attacker to gain code execution on the affected Ajenti server, compromising confidentiality, integrity, and availability of the system.
Affected products
- Ajenti Ajenti < 2.2.13
Identifiers
- CVE-2026-27975
- GHSA-vcw3-r3fx-j444
Timeline
- 2026-02-25: disclosed
- 2026-10-27: advisory
- 2026-02-25: patched