LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27975: Ajenti has a potential Remote Code Execution

Ajenti is a Linux and BSD modular server admin panel. Prior to version 2.2.13, an unauthenticated user could gain access to a server to execute arbitrary code on this server. This is fixed in the version 2.2.13.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Ajenti versions before 2.2.13 can allow an unauthenticated attacker to execute arbitrary code on the server. Because Ajenti is an administrative control panel, compromise could lead to full server control. The vendor advisory says version 2.2.13 fixes the issue.

Executive priority

Treat as urgent for any exposed Ajenti server. This is a remote unauthenticated code execution risk against an admin panel, with high potential business impact if exploited. Patch quickly and reduce exposure.

Technical view

CVE-2026-27975 affects ajenti/ajenti prior to 2.2.13. The issue is categorized as CWE-284 and scored CVSS 4.0 8.1 high, with network access, low complexity, no privileges, and no user interaction required. The impact is high for confidentiality, integrity, and availability of the vulnerable server.

Likely exposure

Exposure is likely where Ajenti is deployed on Linux or BSD servers and reachable by untrusted networks. Internet-facing admin panels are the highest concern. The provided sources do not list specific default ports, deployment patterns, or affected operating system versions.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation with low attack complexity. The source bundle does not indicate known active exploitation, and KEV status is false. No exploit details are provided in the cited sources.

Researcher notes

Evidence is limited to the CVE record, GitHub advisory, and 2.2.13 release reference. The advisory states unauthenticated arbitrary code execution before 2.2.13. No public exploit, attack path detail, or workaround beyond the fixed version is included in the provided sources.

Mitigation direction

  • Upgrade Ajenti to version 2.2.13 or later.
  • Prioritize internet-facing Ajenti instances first.
  • Restrict Ajenti access to trusted administrative networks where possible.
  • Review vendor advisory and release notes for additional guidance.
  • Monitor affected servers for suspicious administrative or process activity.

Validation and detection

  • Inventory all servers running Ajenti.
  • Confirm each Ajenti version is 2.2.13 or later.
  • Identify whether Ajenti is reachable from the internet.
  • Check change records for timely upgrade completion.
  • Review logs for unusual access before patching.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27975 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.1High
CVSS 4.0 vector shape for CVE-2026-27975Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ajentiajenti< 2.2.13Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.